From: "Song, BinX" <binx.song@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Dong, Eric" <eric.dong@intel.com>,
"lersek@redhat.com" <lersek@redhat.com>,
"Ni, Ruiyu" <ruiyu.ni@intel.com>
Subject: Re: [PATCH V2] UefiCpuPkg: Keep library class header file definition independent
Date: Thu, 21 Dec 2017 11:57:00 +0000 [thread overview]
Message-ID: <559D2DF22BC9A3468B4FA1AA547F0EF1025C73B9@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5A7DEEE74@ORSMSX113.amr.corp.intel.com>
Hi Mike,
Thanks for your suggestion.
After discussion with Eric, I know there is a function named IsCpuFeatureSupported() to do the feature valid/invalid check.
User should do IsCpuFeatureSupported() check first and then RegisterCpuFeature().
So there is no need to add any code to do the same work, I will roll back the patch which has been checked in before.
Best Regards,
Bell Song
> -----Original Message-----
> From: Kinney, Michael D
> Sent: Tuesday, December 19, 2017 7:21 AM
> To: Song, BinX <binx.song@intel.com>; edk2-devel@lists.01.org; Kinney,
> Michael D <michael.d.kinney@intel.com>
> Cc: Dong, Eric <eric.dong@intel.com>; lersek@redhat.com; Ni, Ruiyu
> <ruiyu.ni@intel.com>
> Subject: RE: [PATCH V2] UefiCpuPkg: Keep library class header file definition
> independent
>
> This still does not work because a library instance that
> registers a new CPU feature may want to use a new feature
> bit larger than MAX. This change moves the define
> from the RegisterCpuFeaturesLib library class to the
> implementation of the RegisterCpuFeaturesLibs.
>
> The components that know the maximum bit number are the
> NULL lib instances that register CPU features (e.g.
> CpuCommonFeaturesLib) and the platform developer that
> that provides the set of NULL lib instances in a platform
> DSC file and the associated PCDs. For example, the
> following DSC fragment only specifies a single NULL lib
> instance that registers CPU features. However, it is
> legal to provide additional NULL lib instances from
> Si packages.
>
> UefiCpuPkg/CpuFeatures/CpuFeaturesDxe.inf {
> <LibraryClasses>
>
> NULL|UefiCpuPkg/Library/CpuCommonFeaturesLib/CpuCommonFeaturesLib
> .inf
> }
>
> The maximum size of the bitmask for CPU features is known
> by the size of the PCD called PcdCpuFeaturesSupport that
> has a DEC default value based on CpuCommonFeaturesLib but
> can be set to a larger size based on the maximum bit used
> by all the NULL lib instances.
>
> So maybe the valid check should just verify that the bit
> number passed in is < PcdGetSize (PcdCpuFeaturesSupport) * 8.
> This eliminates the use of the #define value and uses an
> existing PCD.
>
> Thanks,
>
> Mike
>
> > -----Original Message-----
> > From: Song, BinX
> > Sent: Sunday, December 17, 2017 9:37 PM
> > To: edk2-devel@lists.01.org
> > Cc: Dong, Eric <eric.dong@intel.com>;
> > lersek@redhat.com; Ni, Ruiyu <ruiyu.ni@intel.com>;
> > Kinney, Michael D <michael.d.kinney@intel.com>
> > Subject: [PATCH V2] UefiCpuPkg: Keep library class
> > header file definition independent
> >
> > V2:
> > Move CPU_FEATURE_MAX definition from header file to C
> > file.
> > V1:
> > Keep library class header file definition independent
> >
> > Cc: Eric Dong <eric.dong@intel.com>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Bell Song <binx.song@intel.com>
> > ---
> > UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> > | 5 -----
> >
> > .../Library/RegisterCpuFeaturesLib/RegisterCpuFeaturesL
> > ib.c | 11 ++++++-----
> > 2 files changed, 6 insertions(+), 10 deletions(-)
> >
> > diff --git
> > a/UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> > b/UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> > index fc3ccda..9331e49 100644
> > ---
> > a/UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> > +++
> > b/UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> > @@ -71,11 +71,6 @@
> > #define CPU_FEATURE_APIC_TPR_UPDATE_MESSAGE
> > (32+9)
> > #define CPU_FEATURE_ENERGY_PERFORMANCE_BIAS
> > (32+10)
> > #define CPU_FEATURE_PPIN
> > (32+11)
> > -//
> > -// Currently, CPU_FEATURE_PROC_TRACE is the MAX
> > feature we support.
> > -// If you define a feature bigger than it, please also
> > replace it
> > -// in RegisterCpuFeatureLibIsFeatureValid function.
> > -//
> > #define CPU_FEATURE_PROC_TRACE
> > (32+12)
> >
> > #define CPU_FEATURE_BEFORE_ALL
> > BIT27
> > diff --git
> > a/UefiCpuPkg/Library/RegisterCpuFeaturesLib/RegisterCpu
> > FeaturesLib.c
> > b/UefiCpuPkg/Library/RegisterCpuFeaturesLib/RegisterCpu
> > FeaturesLib.c
> > index 6ec26e1..afc424c 100644
> > ---
> > a/UefiCpuPkg/Library/RegisterCpuFeaturesLib/RegisterCpu
> > FeaturesLib.c
> > +++
> > b/UefiCpuPkg/Library/RegisterCpuFeaturesLib/RegisterCpu
> > FeaturesLib.c
> > @@ -13,6 +13,10 @@
> > **/
> >
> > #include "RegisterCpuFeatures.h"
> > +//
> > +// Please keep CPU_FEATURE_MAX as the max CPU feature
> > +//
> > +#define CPU_FEATURE_MAX (32+12)
> >
> > /**
> > Checks if two CPU feature bit masks are equal.
> > @@ -97,11 +101,8 @@ RegisterCpuFeatureLibIsFeatureValid
> > (
> >
> > Data = Feature;
> > Data &= ~(CPU_FEATURE_BEFORE | CPU_FEATURE_AFTER |
> > CPU_FEATURE_BEFORE_ALL | CPU_FEATURE_AFTER_ALL);
> > - //
> > - // Currently, CPU_FEATURE_PROC_TRACE is the MAX
> > feature we support.
> > - // If you define a feature bigger than it, please
> > replace it at below.
> > - //
> > - if (Data > CPU_FEATURE_PROC_TRACE) {
> > +
> > + if (Data > CPU_FEATURE_MAX) {
> > DEBUG ((DEBUG_ERROR, "Invalid CPU feature: 0x%x ",
> > Feature));
> > return FALSE;
> > }
> > --
> > 2.10.2.windows.1
prev parent reply other threads:[~2017-12-21 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 5:36 [PATCH V2] UefiCpuPkg: Keep library class header file definition independent Song, BinX
2017-12-18 23:20 ` Kinney, Michael D
2017-12-21 11:57 ` Song, BinX [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=559D2DF22BC9A3468B4FA1AA547F0EF1025C73B9@SHSMSX101.ccr.corp.intel.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