[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH RFC 05/31] xen/x86: Collect more CPUID feature words
>>> On 16.12.15 at 22:24, <andrew.cooper3@xxxxxxxxxx> wrote: > --- a/xen/arch/x86/cpu/amd.c > +++ b/xen/arch/x86/cpu/amd.c > @@ -481,7 +481,7 @@ static void __devinit init_amd(struct cpuinfo_x86 *c) > > if (c->extended_cpuid_level >= 0x80000007) { > c->x86_power = cpuid_edx(0x80000007); > - if (c->x86_power & (1<<8)) { > + if (c->x86_power & cpufeat_mask(X86_FEATURE_ITSC)) { generic_identify() has already run by the time we get here, so no need to re-read cpuid_edx() (interestingly enough you leverage this in init_intel()). > --- a/xen/arch/x86/cpuid/cpuid.c > +++ b/xen/arch/x86/cpuid/cpuid.c > @@ -103,6 +103,12 @@ const uint32_t known_features[XEN_NR_FEATURESET_ENTRIES] > = > cpufeat_mask(X86_FEATURE_RDSEED) > | > cpufeat_mask(X86_FEATURE_ADX) > | > cpufeat_mask(X86_FEATURE_SMAP)), > + > + [cpufeat_word(X86_FEATURE_PREFETCHWT1)] = > (cpufeat_mask(X86_FEATURE_PREFETCHWT1)), > + > + [cpufeat_word(X86_FEATURE_ITSC)] = (cpufeat_mask(X86_FEATURE_ITSC)), > + > + [cpufeat_word(X86_FEATURE_CLZERO)] = (cpufeat_mask(X86_FEATURE_CLZERO)), > }; Are these indeed the only ones in their groups that can be safely marked "known"? Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |