Lines Matching full:cpuid

19 CPUID to find out what the target machine supports and what not.
23 said CPU supports CPUID faulting - userspace can simply probe for the
32 kernel has *enabled* and *supports*. As in: the CPUID feature flag is
64 tools/arch/x86/kcpuid and cpuid(1).
73 unlikely. KVM can synthesize the CPUID bit and the KVM guest can simply
74 query CPUID and figure out what the hypervisor supports and what not. As
82 Feature flags can be derived from the contents of CPUID leaves
85 These feature definitions are organized mirroring the layout of CPUID
93 Flags can be from scattered CPUID-based features
96 Hardware features enumerated in sparsely populated CPUID leaves get
97 software-defined values. Still, CPUID needs to be queried to determine
100 checked at runtime in the respective CPUID leaf [EAX=f, ECX=0] bit EDX[1].
102 The intent of scattering CPUID leaves is to not bloat struct
103 cpuinfo_x86.x86_capability[] unnecessarily. For instance, the CPUID leaf
104 [EAX=7, ECX=0] has 30 features and is dense, but the CPUID leaf [EAX=7, EAX=1]
178 Even though the feature will still be detected via CPUID, the kernel disables