x86/cpuid: Disntangle, and PPIN
cover x86/cpuid: Disntangle, and PPIN
Work to disentangle new feature addition, using PPIN as an example.
Andrew Cooper (1):
x86/cpuid: Disentangle logic for new feature leaves
Jan Beulich (2):
x86/cpuid: Infrastructure for leaf 0x00000007:1.ebx x86/Intel: use CPUID bit to determine PPIN availability
tools/misc/xen-cpuid.c | 6 +++ xen/arch/x86/cpu/common.c | 57 +++++++++++++++-------------- xen/arch/x86/cpu/mcheck/mce_intel.c | 10 ++++- xen/include/public/arch-x86/cpufeatureset.h | 3 ++ xen/include/xen/lib/x86/cpuid.h | 7 ++++ xen/tools/gen-cpuid.py | 2 + 6 files changed, 56 insertions(+), 29 deletions(-)
Signature · 1 line
2.11.0
PATCH 1/3 x86/cpuid: Disentangle logic for new feature leaves
Adding a new feature leaf is a reasonable amount of boilerplate and for the patch to build, at least one feature from the new leaf needs defining. This typically causes two non-trivial changes to be merged together.
First, have gen-cpuid.py write out some extra placeholder defines:
#define CPUID_BITFIELD_11 bool :1, :1, lfence_dispatch:1, ... #define CPUID_BITFIELD_12 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_13 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_14 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_15 uint32_t :32 /* placeholder */
This allows DECL_BITFIELD() to be added to struct cpuid_policy without requiring a XEN_CPUFEATURE() declared for the leaf. The choice of 4 is arbitrary, and allows us to add more than one leaf at a time if necessary.
Second, rework generic_identify() to not use feature leaf names.
The choice of deriving the index from a feature was to avoid mismatches, but its correctness depends on bugs like c/s 249e0f1d8f20 ("x86/cpuid: Fix TSXLDTRK definition") not happening.
Switch to using FEATURESET_* just like the policy/featureset helpers. This breaks the cognitive complexity of needing to know which leaf a specifically named feature should reside in, and is shorter to write. It is also far easier to identify as correct at a glance, given the correlation with the CPUID leaf being read.
In addition, tidy up some other bits of generic_identify()
* Drop leading zeros from leaf numbers.
* Don't use a locked update for X86_FEATURE_APERFMPERF.
* Rework extended_cpuid_level calculation to avoid setting it twice.
* Use "leaf >= $N" consistently so $N matches with the CPUID input.
---
CC: Jan Beulich <[email protected]>
CC: Roger Pau Monné <[email protected]>
CC: Wei Liu <[email protected]>
--- xen/arch/x86/cpu/common.c | 54 +++++++++++++++++++++++------------------------ xen/tools/gen-cpuid.py | 2 ++ 2 files changed, 29 insertions(+), 27 deletions(-)
xen/arch/x86/cpu/common.c +27 -27
@@ -379,7 +379,7 @@ static void generic_identify(struct cpuinfo_x86 *c)u32 eax, ebx, ecx, edx, tmp;/* Get vendor name */ -cpuid (0x00000000 , &c->cpuid_level, &ebx, &ecx, &edx); +cpuid (0 , &c->cpuid_level, &ebx, &ecx, &edx); *(u32 *)&c->x86_vendor_id[0 ] = ebx; *(u32 *)&c->x86_vendor_id[8 ] = ecx; *(u32 *)&c->x86_vendor_id[4 ] = edx;
@@ -394,7 +394,7 @@ static void generic_identify(struct cpuinfo_x86 *c)/* Note that the vendor-specific code below might override */ /* Model and family information. */ -cpuid (0x00000001 , &eax, &ebx, &ecx, &edx); +cpuid (1 , &eax, &ebx, &ecx, &edx); c->x86 =get_cpu_family (eax, &c->x86_model, &c->x86_mask); c->apicid =phys_pkg_id ((ebx >>24 ) &0xFF ,0 ); c->phys_proc_id = c->apicid;
@@ -404,53 +404,53 @@ static void generic_identify(struct cpuinfo_x86 *c)/* c_early_init() may have adjusted cpuid levels/features. Reread. */ c->cpuid_level =cpuid_eax (0 ); -cpuid (0x00000001 , &eax, &ebx, &ecx, &edx); - c->x86_capability[cpufeat_word (X86_FEATURE_FPU )] = edx; - c->x86_capability[cpufeat_word (X86_FEATURE_SSE3 )] = ecx; +cpuid (1 , &eax, &ebx, + &c->x86_capability[FEATURESET_1c], + &c->x86_capability[FEATURESET_1d]);if (cpu_has (c,X86_FEATURE_CLFLUSH ) ) c->x86_clflush_size = ((ebx >>8 ) &0xff ) *8 ;if ( (c->cpuid_level >=CPUID_PM_LEAF ) && (cpuid_ecx (CPUID_PM_LEAF ) &CPUID6_ECX_APERFMPERF_CAPABILITY ) ) -set_bit (X86_FEATURE_APERFMPERF , c->x86_capability); +__set_bit (X86_FEATURE_APERFMPERF , c->x86_capability); + + eax =cpuid_eax (0x80000000 ); +if ((eax >>16 ) ==0x8000 ) + c->extended_cpuid_level = eax;/* AMD-defined flags: level 0x80000001 */ - c->extended_cpuid_level =cpuid_eax (0x80000000 ); -if ((c->extended_cpuid_level >>16 ) !=0x8000 ) - c->extended_cpuid_level =0 ; -if (c->extended_cpuid_level >0x80000000 ) +if (c->extended_cpuid_level >=0x80000001 )cpuid (0x80000001 , &tmp, &tmp, - &c->x86_capability[cpufeat_word (X86_FEATURE_LAHF_LM )], - &c->x86_capability[cpufeat_word (X86_FEATURE_SYSCALL )]); + &c->x86_capability[FEATURESET_e1c], + &c->x86_capability[FEATURESET_e1d]);if (c->extended_cpuid_level >=0x80000004 )get_model_name (c);/* Default name */ if (c->extended_cpuid_level >=0x80000007 ) - c->x86_capability[cpufeat_word (X86_FEATURE_ITSC )] - =cpuid_edx (0x80000007 ); + c->x86_capability[FEATURESET_e7d] =cpuid_edx (0x80000007 );if (c->extended_cpuid_level >=0x80000008 ) - c->x86_capability[cpufeat_word (X86_FEATURE_CLZERO )] - =cpuid_ebx (0x80000008 ); + c->x86_capability[FEATURESET_e8b] =cpuid_ebx (0x80000008 );if (c->extended_cpuid_level >=0x80000021 ) - c->x86_capability[cpufeat_word (X86_FEATURE_LFENCE_DISPATCH )] - =cpuid_eax (0x80000021 ); + c->x86_capability[FEATURESET_e21a] =cpuid_eax (0x80000021 );/* Intel-defined flags: level 0x00000007 */ -if ( c->cpuid_level >=0x00000007 ) { -cpuid_count (0x00000007 ,0 , &eax, - &c->x86_capability[cpufeat_word (X86_FEATURE_FSGSBASE )], - &c->x86_capability[cpufeat_word (X86_FEATURE_PKU )], - &c->x86_capability[cpufeat_word (X86_FEATURE_AVX512_4VNNIW )]); -if (eax >0 ) -cpuid_count (0x00000007 ,1 , - &c->x86_capability[cpufeat_word (X86_FEATURE_AVX512_BF16 )], +if (c->cpuid_level >=7 ) { +uint32_t max_subleaf; + +cpuid_count (7 ,0 , &max_subleaf, + &c->x86_capability[FEATURESET_7b0], + &c->x86_capability[FEATURESET_7c0], + &c->x86_capability[FEATURESET_7d0]); +if (max_subleaf >=1 ) +cpuid_count (7 ,1 , + &c->x86_capability[FEATURESET_7a1], &tmp, &tmp, &tmp); }if (c->cpuid_level >=0xd )cpuid_count (0xd ,1 , - &c->x86_capability[cpufeat_word (X86_FEATURE_XSAVEOPT )], + &c->x86_capability[FEATURESET_Da1], &tmp, &tmp, &tmp); }
xen/tools/gen-cpuid.py +2 -0
@@ -423,6 +423,8 @@ def write_results(state): """) + state.bitfields += ["uint32_t :32 /* placeholder */"] * 4 + for idx, text in enumerate(state.bitfields): state.output.write( "#define CPUID_BITFIELD_%d \\\n %s\n\n"
Signature · 1 line
2.11.0
Re: [PATCH 1/3] x86/cpuid: Disentangle logic for new feature leaves
Quoted 12 lines · Andrew Cooper
Adding a new feature leaf is a reasonable amount of boilerplate and for the patch to build, at least one feature from the new leaf needs defining. This typically causes two non-trivial changes to be merged together.
First, have
gen-cpuid.pywrite out some extra placeholder defines:#define CPUID_BITFIELD_11 bool :1, :1, lfence_dispatch:1, ... #define CPUID_BITFIELD_12 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_13 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_14 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_15 uint32_t :32 /* placeholder */
Quoted 5 lines
This allows
DECL_BITFIELD()to be added to structcpuid_policywithout requiring aXEN_CPUFEATURE()declared for the leaf. The choice of 4 is arbitrary, and allows us to add more than one leaf at a time if necessary.Second, rework
generic_identify()to not use feature leaf names.
This should say "not use specific feature names."
Fixed locally.
~Andrew
Quoted 17 lines
The choice of deriving the index from a feature was to avoid mismatches, but its correctness depends on bugs like c/s
249e0f1d8f20("x86/cpuid: Fix TSXLDTRK definition") not happening.Switch to using FEATURESET_* just like the policy/featureset helpers. This breaks the cognitive complexity of needing to know which leaf a specifically named feature should reside in, and is shorter to write. It is also far easier to identify as correct at a glance, given the correlation with the CPUID leaf being read.
In addition, tidy up some other bits of
generic_identify()
* Drop leading zeros from leaf numbers.
* Don't use a locked update forX86_FEATURE_APERFMPERF.
* Reworkextended_cpuid_levelcalculation to avoid setting it twice.
* Use "leaf >= $N" consistently so $N matches with the CPUID input.Signed-off-by Andrew Cooper <[email protected]>
Re: [PATCH 1/3] x86/cpuid: Disentangle logic for new feature leaves
In reply to Andrew CooperQuoted 28 lines · Andrew Cooper
Adding a new feature leaf is a reasonable amount of boilerplate and for the patch to build, at least one feature from the new leaf needs defining. This typically causes two non-trivial changes to be merged together.
First, have
gen-cpuid.pywrite out some extra placeholder defines:#define CPUID_BITFIELD_11 bool :1, :1, lfence_dispatch:1, ... #define CPUID_BITFIELD_12 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_13 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_14 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_15 uint32_t :32 /* placeholder */This allows
DECL_BITFIELD()to be added to structcpuid_policywithout requiring aXEN_CPUFEATURE()declared for the leaf. The choice of 4 is arbitrary, and allows us to add more than one leaf at a time if necessary.Second, rework
generic_identify()to not use feature leaf names.The choice of deriving the index from a feature was to avoid mismatches, but its correctness depends on bugs like c/s
249e0f1d8f20("x86/cpuid: Fix TSXLDTRK definition") not happening.Switch to using FEATURESET_* just like the policy/featureset helpers. This breaks the cognitive complexity of needing to know which leaf a specifically named feature should reside in, and is shorter to write. It is also far easier to identify as correct at a glance, given the correlation with the CPUID leaf being read.
Quoted 7 lines
In addition, tidy up some other bits of
generic_identify()
* Drop leading zeros from leaf numbers.
* Don't use a locked update forX86_FEATURE_APERFMPERF.
* Reworkextended_cpuid_levelcalculation to avoid setting it twice.
* Use "leaf >= $N" consistently so $N matches with the CPUID input.Signed-off-by Andrew Cooper <[email protected]>
I will admit that I'm not sure yet whether I will want to break up the KeyLocker patch just like you did with the PPIN one.
The one thing that worries me some that there's still the unvalidated connection between FEATURESET_* and the numbers used in the public cpufeatureset.h. But I have no good idea (yet) for a build-time check.
Jan
Re: [PATCH 1/3] x86/cpuid: Disentangle logic for new feature leaves
Quoted 29 lines · Jan Beulich
Quoted 28 lines · Andrew Cooper
Adding a new feature leaf is a reasonable amount of boilerplate and for the patch to build, at least one feature from the new leaf needs defining. This typically causes two non-trivial changes to be merged together.
First, have
gen-cpuid.pywrite out some extra placeholder defines:#define CPUID_BITFIELD_11 bool :1, :1, lfence_dispatch:1, ... #define CPUID_BITFIELD_12 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_13 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_14 uint32_t :32 /* placeholder */ #define CPUID_BITFIELD_15 uint32_t :32 /* placeholder */This allows
DECL_BITFIELD()to be added to structcpuid_policywithout requiring aXEN_CPUFEATURE()declared for the leaf. The choice of 4 is arbitrary, and allows us to add more than one leaf at a time if necessary.Second, rework
generic_identify()to not use feature leaf names.The choice of deriving the index from a feature was to avoid mismatches, but its correctness depends on bugs like c/s
249e0f1d8f20("x86/cpuid: Fix TSXLDTRK definition") not happening.Switch to using FEATURESET_* just like the policy/featureset helpers. This breaks the cognitive complexity of needing to know which leaf a specifically named feature should reside in, and is shorter to write. It is also far easier to identify as correct at a glance, given the correlation with the CPUID leaf being read.
Quoted 8 lines
Quoted 7 lines
In addition, tidy up some other bits of
generic_identify()
* Drop leading zeros from leaf numbers.
* Don't use a locked update forX86_FEATURE_APERFMPERF.
* Reworkextended_cpuid_levelcalculation to avoid setting it twice.
* Use "leaf >= $N" consistently so $N matches with the CPUID input.Signed-off-by Andrew Cooper <[email protected]>Reviewed-by Jan Beulich <[email protected]>
Thanks.
Quoted 7 lines
I will admit that I'm not sure yet whether I will want to break up the KeyLocker patch just like you did with the PPIN one.
The one thing that worries me some that there's still the unvalidated connection between FEATURESET_* and the numbers used in the public
cpufeatureset.h. But I have no good idea (yet) for a build-time check.
I was also struggling with that. One thing I considered was having some semantic structure to
/* Intel-defined CPU features, CPUID level 0x00000007:1.ebx, word 12 */
and have FEATURESET_* written automatically too, but I can't think of a nice way of organising this right now.
~Andrew
PATCH 2/3 x86/cpuid: Infrastructure for leaf 0x00000007:1.ebx
In reply to Andrew CooperFrom: Jan Beulich <[email protected]>
---
CC: Jan Beulich <[email protected]>
CC: Roger Pau Monné <[email protected]>
CC: Wei Liu <[email protected]>
Split in two, rebase.
--- tools/misc/xen-cpuid.c | 5 +++++ xen/arch/x86/cpu/common.c | 3 ++- xen/include/public/arch-x86/cpufeatureset.h | 2 ++ xen/include/xen/lib/x86/cpuid.h | 7 +++++++ 4 files changed, 16 insertions(+), 1 deletion(-)
tools/misc/xen-cpuid.c +5 -0
@@ -195,6 +195,10 @@ static const char *const str_e21a[32] = [ 6] = "nscb", }; +static const char *const str_7b1[32 ] = +{ +}; + static const struct { const char *name; const char *abbr;
@@ -213,6 +217,7 @@ static const struct { { "0x00000007:0.edx", "7d0", str_7d0 }, { "0x00000007:1.eax", "7a1", str_7a1 }, { "0x80000021.eax", "e21a", str_e21a }, + { "0x00000007:1.ebx", "7b1", str_7b1 }, };#define COL_ALIGN "18"
xen/arch/x86/cpu/common.c +2 -1
@@ -445,7 +445,8 @@ static void generic_identify(struct cpuinfo_x86 *c)if (max_subleaf >=1 )cpuid_count (7 ,1 , &c->x86_capability[FEATURESET_7a1], - &tmp, &tmp, &tmp); + &c->x86_capability[FEATURESET_7b1], + &tmp, &tmp); }if (c->cpuid_level >=0xd )
xen/include/public/arch-x86/cpufeatureset.h +2 -0
@@ -299,6 +299,8 @@ XEN_CPUFEATURE(FSRCS, 10*32+12) /*A Fast Short REP CMPSB/SCASB */ XEN_CPUFEATURE(LFENCE_DISPATCH, 11*32+ 2) /*A LFENCE always serializing */XEN_CPUFEATURE (NSCB ,11 *32 +6 )/*A Null Selector Clears Base (and limit too) */ +/* Intel-defined CPU features, CPUID level 0x00000007:1.ebx, word 12 */ +#endif /* XEN_CPUFEATURE */ /* Clean up from a default include. Close the enum (for C). */
xen/include/xen/lib/x86/cpuid.h +7 -0
@@ -16,6 +16,7 @@#define FEATURESET_7d0 9/* 0x00000007:0.edx */ #define FEATURESET_7a1 10/* 0x00000007:1.eax */ #define FEATURESET_e21a 11/* 0x80000021.eax */ +#define FEATURESET_7b1 12/* 0x00000007:1.ebx */ struct cpuid_leaf {
@@ -188,6 +189,10 @@ struct cpuid_policyuint32_t _7a1; struct { DECL_BITFIELD(7a1); }; }; +union { +uint32_t _7b1; + struct { DECL_BITFIELD(7b1); }; + }; }; } feat;
@@ -327,6 +332,7 @@ static inline void cpuid_policy_to_featureset( fs[FEATURESET_7d0] = p->feat._7d0; fs[FEATURESET_7a1] = p->feat._7a1; fs[FEATURESET_e21a] = p->extd.e21a; + fs[FEATURESET_7b1] = p->feat._7b1; }/* Fill in a CPUID policy from a featureset bitmap. */
@@ -345,6 +351,7 @@ static inline void cpuid_featureset_to_policy( p->feat._7d0 = fs[FEATURESET_7d0]; p->feat._7a1 = fs[FEATURESET_7a1]; p->extd.e21a = fs[FEATURESET_e21a]; + p->feat._7b1 = fs[FEATURESET_7b1]; }static inline uint64_t cpuid_policy_xcr0_max (const struct cpuid_policy *p)
Signature · 1 line
2.11.0
Re: [PATCH 2/3] x86/cpuid: Infrastructure for leaf 0x00000007:1.ebx
Quoted 4 lines · Andrew Cooper
From: Jan Beulich <[email protected]>
Signed-off-by Jan Beulich <[email protected]>Signed-off-by Andrew Cooper <[email protected]>
Considering what patch 1 does to the code, would you mind dropping the 0x0000000 number prefix from the subject?
Jan
Re: [PATCH 2/3] x86/cpuid: Infrastructure for leaf 0x00000007:1.ebx
Quoted 7 lines · Jan Beulich
Quoted 4 lines · Andrew Cooper
From: Jan Beulich <[email protected]>
Signed-off-by Jan Beulich <[email protected]>Signed-off-by Andrew Cooper <[email protected]>Considering what patch 1 does to the code, would you mind dropping the
0x0000000number prefix from the subject?
Oops, yes. Done.
~Andrew
PATCH 3/3 x86/Intel: use CPUID bit to determine PPIN availability
In reply to Andrew CooperFrom: Jan Beulich <[email protected]>
As of SDM revision 076 there is a CPUID bit for this functionality. Use it to amend the existing model-based logic.
---
CC: Jan Beulich <[email protected]>
CC: Roger Pau Monné <[email protected]>
CC: Wei Liu <[email protected]>
Split in two.
--- tools/misc/xen-cpuid.c | 1 + xen/arch/x86/cpu/mcheck/mce_intel.c | 10 +++++++++- xen/include/public/arch-x86/cpufeatureset.h | 1 + 3 files changed, 11 insertions(+), 1 deletion(-)
tools/misc/xen-cpuid.c +1 -0
@@ -197,6 +197,7 @@ static const char *const str_e21a[32] =static const char *const str_7b1[32 ] = { + [0 ] ="ppin" , }; static const struct {
xen/arch/x86/cpu/mcheck/mce_intel.c +9 -1
@@ -859,12 +859,20 @@ static void intel_init_ppin(const struct cpuinfo_x86 *c)/* * Even if testing the presence of the MSR would be enough, we don't * want to risk the situation where other models reuse this MSR for -* other purposes. +* other purposes. Despite the late addition of a CPUID bit (rendering +* the MSR architectural), keep using the same detection logic there. */ switch ( c->x86_model ) {uint64_t val; +default : +if ( !cpu_has (c,X86_FEATURE_INTEL_PPIN ) ) + { + ppin_msr =0 ; +return ; + } + fallthrough;case 0x3e :/* IvyBridge X */ case 0x3f :/* Haswell X */ case 0x4f :/* Broadwell X */
xen/include/public/arch-x86/cpufeatureset.h +1 -0
@@ -300,6 +300,7 @@ XEN_CPUFEATURE(LFENCE_DISPATCH, 11*32+ 2) /*A LFENCE always serializing */XEN_CPUFEATURE (NSCB ,11 *32 +6 )/*A Null Selector Clears Base (and limit too) */ /* Intel-defined CPU features, CPUID level 0x00000007:1.ebx, word 12 */ +XEN_CPUFEATURE(INTEL_PPIN, 12*32+ 0) /* Protected Processor Inventory Number */#endif /* XEN_CPUFEATURE */
Signature · 1 line
2.11.0