From: "Song, BinX" <binx.song@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "lersek@redhat.com" <lersek@redhat.com>,
"Dong, Eric" <eric.dong@intel.com>
Subject: Re: [PATCH] UefiCpuPkg: Check invalid RegisterCpuFeature parameter
Date: Mon, 11 Dec 2017 10:00:27 +0000 [thread overview]
Message-ID: <559D2DF22BC9A3468B4FA1AA547F0EF1025C1D4F@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <03c857ea-b316-5307-5489-e5ddf967b295@Intel.com>
Hi Ray,
Below is my opinions for your 2 questions:
1. Can we rename this function name to "RegisterCpuFeatureLibIsFeatureValid"?
[Bell]: In content of RegisterCpuFeaturesLib.c, there is a function named IsBitMaskMatchCheck(), it's my function's base, they have similar function - a small valid/invalid check,
So I think it is better to keep them align.
2. Can we just say "CPU_FEATURE_PROC_TRACE" is the MAX feature we support?
[Bell]: Discussed with Eric before, we should not define this as a MAX feature for future extension purpose.
Best Regards,
Bell Song
> -----Original Message-----
> From: Ni, Ruiyu
> Sent: Monday, December 11, 2017 5:40 PM
> To: Song, BinX <binx.song@intel.com>; edk2-devel@lists.01.org
> Cc: lersek@redhat.com; Dong, Eric <eric.dong@intel.com>
> Subject: Re: [edk2] [PATCH] UefiCpuPkg: Check invalid RegisterCpuFeature
> parameter
>
> On 12/11/2017 4:16 PM, Song, BinX wrote:
> > Check and assert invalid RegisterCpuFeature function parameter
> >
> > 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>
> > ---
> > .../Include/Library/RegisterCpuFeaturesLib.h | 4 ++++
> > .../RegisterCpuFeaturesLib.c | 28 ++++++++++++++++++++++
> > 2 files changed, 32 insertions(+)
> >
> > diff --git a/UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> b/UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> > index 9331e49..54244cd 100644
> > --- a/UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> > +++ b/UefiCpuPkg/Include/Library/RegisterCpuFeaturesLib.h
> > @@ -72,6 +72,10 @@
> > #define CPU_FEATURE_ENERGY_PERFORMANCE_BIAS (32+10)
> > #define CPU_FEATURE_PPIN (32+11)
> > +//
> > +// When you add new CPU features, please also replace the minor CPU
> feature
> > +// with the max CPU feature in the IsFeatureValidCheck() function.
> > +//
> > #define CPU_FEATURE_PROC_TRACE (32+12)
> >
> > #define CPU_FEATURE_BEFORE_ALL BIT27
> > #define CPU_FEATURE_AFTER_ALL BIT28
> > diff --git
> a/UefiCpuPkg/Library/RegisterCpuFeaturesLib/RegisterCpuFeaturesLib.c
> b/UefiCpuPkg/Library/RegisterCpuFeaturesLib/RegisterCpuFeaturesLib.c
> > index dd6a82b..f75d900 100644
> > ---
> a/UefiCpuPkg/Library/RegisterCpuFeaturesLib/RegisterCpuFeaturesLib.c
> > +++
> b/UefiCpuPkg/Library/RegisterCpuFeaturesLib/RegisterCpuFeaturesLib.c
> > @@ -81,6 +81,33 @@ DumpCpuFeature (
> > }
> >
> > /**
> > + Determines if the CPU feature is valid.
> > +
> > + @param[in] Feature Pointer to CPU feature
> > +
> > + @retval TRUE The CPU feature is valid.
> > + @retval FALSE The CPU feature is invalid.
> > +**/
> > +BOOLEAN
> > +IsFeatureValidCheck (
> Can we rename this function name to
> "RegisterCpuFeatureLibIsFeatureValid"?
>
>
> > + IN UINT32 Feature
> > + )
> > +{
> > + UINT32 Data;
> > +
> > + Data = Feature;
> > + Data &= ~(CPU_FEATURE_BEFORE | CPU_FEATURE_AFTER |
> CPU_FEATURE_BEFORE_ALL | CPU_FEATURE_AFTER_ALL);
> > + //
> > + // Please replace CPU feature below with the MAX one if have.
> Can we just say "CPU_FEATURE_PROC_TRACE" is the MAX feature we
> support?
>
>
> > + //
> > + if (Data > CPU_FEATURE_PROC_TRACE) {
> > + DEBUG ((DEBUG_ERROR, "Invalid CPU feature: 0x%x ", Feature));
> > + return FALSE;
> > + }
> > + return TRUE;
> > +}
> > +
> > +/**
> > Determines if the feature bit mask is in dependent CPU feature bit mask
> buffer.
> >
> > @param[in] FeatureMask Pointer to CPU feature bit mask
> > @@ -444,6 +471,7 @@ RegisterCpuFeature (
> >
> > VA_START (Marker, InitializeFunc);
> > Feature = VA_ARG (Marker, UINT32);
> > + ASSERT (IsFeatureValidCheck(Feature));
> > while (Feature != CPU_FEATURE_END) {
> > ASSERT ((Feature & (CPU_FEATURE_BEFORE | CPU_FEATURE_AFTER))
> > != (CPU_FEATURE_BEFORE | CPU_FEATURE_AFTER));
> >
>
>
> --
> Thanks,
> Ray
next prev parent reply other threads:[~2017-12-11 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 8:16 [PATCH] UefiCpuPkg: Check invalid RegisterCpuFeature parameter Song, BinX
2017-12-11 8:23 ` Dong, Eric
2017-12-11 9:40 ` Ni, Ruiyu
2017-12-11 10:00 ` Song, BinX [this message]
2017-12-12 8:43 ` Ni, Ruiyu
2017-12-13 1:54 ` Song, BinX
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=559D2DF22BC9A3468B4FA1AA547F0EF1025C1D4F@shsmsx102.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