From: Laszlo Ersek <lersek@redhat.com>
To: Leo Duran <leo.duran@amd.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH v2 0/9] Enhanced SMM support to AMD-based x86 systems.
Date: Wed, 4 Oct 2017 12:46:27 +0200 [thread overview]
Message-ID: <2d3efa5a-ad72-bb35-1e6a-b9b78379337c@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5A7DAEE07@ORSMSX113.amr.corp.intel.com>
On 10/04/17 03:22, Kinney, Michael D wrote:
> Leo,
>
> The general design issue here is that a PCD and PCD macro were
> added to a UefiCpuPkg include file Include/Register/SmramSaveStateMap.h.
> This means any library or module that includes this package include
> file will break the build until the PCD is added to the INF file for
> that library or module.
>
> The INF file for a module is supposed to express the PCDs that the
> library or module sources access. We do not expect #include
> statements from package include files to require adding additional
> PCDs.
>
> Updating the code for these values to be detected or configurable
> is a good idea.
>
> One option is to update the C code that currently uses the #define
> names to use the PCD access function directly, instead of adding
> the PcdGetxxx() to the Include/Register/SmramSaveStateMap.h file.
>
> Jiewen's idea to remove the PCD and detect the offset from CPUID
> also looks like a reasonable approach.
In addition to the above, I'd like to request a bit more "telling"
subject lines for the patches. Using the OVMF patch as example,
OvmfPkg: SmmCpuFeaturesLib library.
is not really helpful; I'd consider the following an improvement:
OvmfPkg/SmmCpuFeaturesLib: consume SMRAM Save State Map Offset PCD
66 characters -- we generally limit subjects to 74.
(Of course I realize the patch might entirely be replaced in the next
version, based on Jiewen's and Mike's feedback -- that's OK with me, I
just wanted to give an example.)
Thanks!
Laszlo
prev parent reply other threads:[~2017-10-04 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 22:38 [PATCH v2 0/9] Enhanced SMM support to AMD-based x86 systems Leo Duran
2017-10-03 22:38 ` [PATCH v2 1/9] UefiCpuPkg: UefiCpuPkg.dec Leo Duran
2017-10-03 22:38 ` [PATCH v2 2/9] UefiCpuPkg: PiSmmCpuDxeSmm driver Leo Duran
2017-10-03 22:38 ` [PATCH v2 3/9] UefiCpuPkg: SmmCpuFeaturesLib library Leo Duran
2017-10-03 22:38 ` [PATCH v2 4/9] OvmfPkg: " Leo Duran
2017-10-03 22:38 ` [PATCH v2 5/9] QuarkSocPkg: " Leo Duran
2017-10-03 22:38 ` [PATCH v2 6/9] UefiCpuPkg: Register/SmramSaveStateMap.h Leo Duran
2017-10-03 22:38 ` [PATCH v2 7/9] UefiCpuPkg: PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h Leo Duran
2017-10-03 22:38 ` [PATCH v2 8/9] UefiCpuPkg: PiSmmCpuDxeSmm driver Leo Duran
2017-10-03 22:38 ` [PATCH v2 9/9] UefiCpuPkg: SmmCpuFeaturesLib library Leo Duran
2017-10-04 0:50 ` [PATCH v2 0/9] Enhanced SMM support to AMD-based x86 systems Yao, Jiewen
2017-10-04 1:22 ` Kinney, Michael D
2017-10-04 10:46 ` Laszlo Ersek [this message]
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=2d3efa5a-ad72-bb35-1e6a-b9b78379337c@redhat.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