From: "Liming Gao" <liming.gao@intel.com>
To: Leif Lindholm <leif@nuviainc.com>,
"Javeed, Ashraf" <ashraf.javeed@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
Sean Brogan <sean.brogan@microsoft.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH V4 1/2] MdePkg/Include/IndustryStandard: CXL 1.1 Registers
Date: Tue, 28 Jul 2020 02:07:04 +0000 [thread overview]
Message-ID: <MWHPR11MB16309FA5BF556304091F5A1280730@MWHPR11MB1630.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200727161425.GB1337@vanye>
Leif:
-----Original Message-----
From: Leif Lindholm <leif@nuviainc.com>
Sent: 2020年7月28日 0:14
To: Gao, Liming <liming.gao@intel.com>
Cc: devel@edk2.groups.io; Javeed, Ashraf <ashraf.javeed@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH V4 1/2] MdePkg/Include/IndustryStandard: CXL 1.1 Registers
On Mon, Jul 27, 2020 at 14:55:03 +0000, Gao, Liming wrote:
> > > diff --git a/MdePkg/Include/IndustryStandard/Cxl11.h
> > > b/MdePkg/Include/IndustryStandard/Cxl11.h
> > > new file mode 100644
> > > index 0000000000..933c1ab817
> > > --- /dev/null
> > > +++ b/MdePkg/Include/IndustryStandard/Cxl11.h
> > > @@ -0,0 +1,569 @@
> > > +/** @file
> > > + CXL 1.1 Register definitions
> > > +
> > > + This file contains the register definitions based on the
> > > + Compute Express Link
> > > + (CXL) Specification Revision 1.1.
> > > +
> > > +Copyright (c) 2020, Intel Corporation. All rights reserved.<BR>
> > > +SPDX-License-Identifier: BSD-2-Clause-Patent
> > > +
> > > +**/
> > > +
> > > +#ifndef _CXL11_H_
> > > +#define _CXL11_H_
> >
> > We should not be adding macros with a leading _ - these are intended
> > for toolchain use.
>
> This style is align to other header file. This is the file header
> macro to make sure the header file be included more than once.
Yes. The other headers should also be changed, but in the meantime it would be good to stop adding more incorrect ones.
https://edk2-docs.gitbook.io/edk-ii-c-coding-standards-specification/5_source_files/53_include_files#5-3-5-all-include-file-contents-must-be-protected-by-a-include-guard
[Liming] Thank for your point. I miss this one, too. Now, most cases don't follow this rule. So, there is no good example for the reference.
I agree the rule to apply the strict check for new adding file. I will check whether ECC has this check point.
> > > +
> > > +//
> > > +// CXL Flex Bus Device default device and function number //
> > > +Compute Express Link Specification Revision: 1.1 - Chapter 7.1.1
> > > +//
> > > +#define CXL_DEV_DEV 0
> > > +#define CXL_DEV_FUNC 0
> > > +
> > > +//
> > > +// Ensure proper structure formats // #pragma pack(1)
> >
> > And this pragma has no function whatsoever with regards to any of
> > the register definition structs below. It would be much better if
> > the structs requiring packing (_DEVICE, _PORT, ...) were grouped
> > together and only those were given this treatment.
> >
> > #pragma pack(1) is *not* a safe default.
> >
>
> I know pack(1) is for the compact structure layout.
Yes. And it should be used when structs need to be compacted.
All of the bitfield structs are single-variable structs, so the packing has no effect on them, other than setting the struct alignment requirements to 1 byte, which will not be correct (or efficient) on all architectures.
[Liming] Yes. There is no effect for bitfield structure. This header file still includes some structure, such as CXL_1_1_DVSEC_FLEX_BUS_DEVICE. They may have the compact alignment requirement.
@Javeed, Ashraf, can you conform it?
> > Now, one final comment - and this is more of a project feature
> > suggestion:
> > Industry standard headers is something fairly special, even in
> > comparison with the rest of MdePkg. *I* would certainly like to
> > ensure I don't miss changes or additions to them.
> > Could we set up a dedicated group of reviewers for this folder only?
> > This need not affect the actual maintainership of MdePkg, just
> > ensure more eyeballs (or screen readers, braille terminals, ...) hit
> > updates here?
> >
> > i.e. something like the below to Maintainers.txt:
> >
> > F: MdePkg/Include/IndustryStandard/
> > R: Leif ...
> > R: ...
> > R: ...
> >
>
> This is a good suggestion. IndustryStandard needs more feedback.
> Can you send the patch to update Maintainers.txt?
Sure, I can do that. Any thoughts on others to add than me?
[Liming] Thanks. Laszlo or Sean may be added if they are also interested in IndustryStandard header file.
Thanks
Liming
/
Leif
next prev parent reply other threads:[~2020-07-28 2:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 18:26 [PATCH V4 0/2] CXL Specification Registers Javeed, Ashraf
2020-07-24 18:26 ` [PATCH V4 1/2] MdePkg/Include/IndustryStandard: CXL 1.1 Registers Javeed, Ashraf
2020-07-27 14:24 ` [edk2-devel] [PATCH V4 1/2] MdePkg/Include/IndustryStandard: " Leif Lindholm
2020-07-27 14:55 ` Liming Gao
2020-07-27 16:14 ` Leif Lindholm
2020-07-28 2:07 ` Liming Gao [this message]
2020-07-28 2:22 ` Michael D Kinney
2020-07-28 2:36 ` Ni, Ray
2020-07-28 6:18 ` Javeed, Ashraf
2020-07-28 6:46 ` Javeed, Ashraf
2020-07-24 18:26 ` [PATCH V4 2/2] MdePkg/Include/IndustryStandard: Main CXL header Javeed, Ashraf
2020-07-27 2:35 ` [PATCH V4 0/2] CXL Specification Registers Liming Gao
2020-07-27 3:43 ` Liming Gao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR11MB16309FA5BF556304091F5A1280730@MWHPR11MB1630.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox