From Wikipedia the free encyclopedia

In the x86 architecture, the CPUID instruction (identified by a CPUID opcode) is a processor supplementary instruction (its name derived from CPU Identification) allowing software to discover details of the processor. It was introduced by Intel in 1993 with the launch of the Pentium and SL-enhanced 486 processors.[1]

A program can use the CPUID to determine processor type and whether features such as MMX/SSE are implemented.


Prior to the general availability of the CPUID instruction, programmers would write esoteric machine code which exploited minor differences in CPU behavior in order to determine the processor make and model.[2][3][4][5] With the introduction of the 80386 processor, EDX on reset indicated the revision but this was only readable after reset and there was no standard way for applications to read the value.

Outside the x86 family, developers are mostly still required to use esoteric processes (involving instruction timing or CPU fault triggers) to determine the variations in CPU design that are present.

For example, in the Motorola 680x0 family — that never had a CPUID instruction of any kind — certain specific instructions required elevated privileges. These could be used to tell various CPU family members apart. In the Motorola 68010 the instruction MOVE from SR became privileged. This notable instruction (and state machine) change allowed the 68010 to meet the Popek and Goldberg virtualization requirements. Because the 68000 offered an unprivileged MOVE from SR the 2 different CPUs could be told apart by a CPU error condition being triggered.

While the CPUID instruction is specific to the x86 architecture, other architectures (like ARM) often provide on-chip registers which can be read in prescribed ways to obtain the same sorts of information provided by the x86 CPUID instruction.

Calling CPUID[edit]

The CPUID opcode is 0F A2.

In assembly language, the CPUID instruction takes no parameters as CPUID implicitly uses the EAX register to determine the main category of information returned. In Intel's more recent terminology, this is called the CPUID leaf. CPUID should be called with EAX = 0 first, as this will store in the EAX register the highest EAX calling parameter (leaf) that the CPU implements.

To obtain extended function information CPUID should be called with the most significant bit of EAX set. To determine the highest extended function calling parameter, call CPUID with EAX = 80000000h.

CPUID leaves greater than 3 but less than 80000000 are accessible only when the model-specific registers have IA32_MISC_ENABLE.BOOT_NT4 [bit 22] = 0 (which is so by default). As the name suggests, Windows NT 4.0 until SP6 did not boot properly unless this bit was set,[6] but later versions of Windows do not need it, so basic leaves greater than 4 can be assumed visible on current Windows systems. As of April 2024, basic valid leaves go up to 23h, but the information returned by some leaves are not disclosed in the publicly available documentation, i.e. they are "reserved".

Some of the more recently added leaves also have sub-leaves, which are selected via the ECX register before calling CPUID.

EAX=0: Highest Function Parameter and Manufacturer ID[edit]

This returns the CPU's manufacturer ID string – a twelve-character ASCII string stored in EBX, EDX, ECX (in that order). The highest basic calling parameter (the largest value that EAX can be set to before calling CPUID) is returned in EAX.

Here is a list of processors and the highest function implemented.

Highest Function Parameter
Processors Basic Extended
Earlier Intel 486 CPUID Not Implemented
Later Intel 486 and Pentium 0x01 Not Implemented
Pentium Pro, Pentium II and Celeron 0x02 Not Implemented
Pentium III 0x03 Not Implemented
Pentium 4 0x02 0x8000 0004
Xeon 0x02 0x8000 0004
Pentium M 0x02 0x8000 0004
Pentium 4 with Hyper-Threading 0x05 0x8000 0008
Pentium D (8xx) 0x05 0x8000 0008
Pentium D (9xx) 0x06 0x8000 0008
Core Duo 0x0A 0x8000 0008
Core 2 Duo 0x0A 0x8000 0008
Xeon 3000, 5100, 5200, 5300, 5400 (5000 series) 0x0A 0x8000 0008
Core 2 Duo 8000 series 0x0D 0x8000 0008
Xeon 5200, 5400 series 0x0A 0x8000 0008
Atom 0x0A 0x8000 0008
Nehalem-based processors 0x0B 0x8000 0008
Ivy Bridge-based processors 0x0D 0x8000 0008
Skylake-based processors (proc base & max freq; Bus ref. freq) 0x16 0x8000 0008
System-On-Chip Vendor Attribute Enumeration Main Leaf 0x17 0x8000 0008
Meteor Lake-based processors 0x23 0x8000 0008

The following are known processor manufacturer ID strings:

The following are ID strings used by open source soft CPU cores:

  • "GenuineAO486" – ao486 CPU (old)[13][14]
  • "MiSTer AO486" – ao486 CPU (new)[15][14]
  • "GenuineIntel" – v586 core[16] (this is identical to the Intel ID string)

The following are known ID strings from virtual machines:

  • "MicrosoftXTA" – Microsoft x86-to-ARM[17]
  • "GenuineIntel" – Apple Rosetta 2[18]
  • "VirtualApple" – Newer versions of Apple Rosetta 2

For instance, on a GenuineIntel processor values returned in EBX is 0x756e6547, EDX is 0x49656e69 and ECX is 0x6c65746e. The following example code displays the vendor ID string as well as the highest calling parameter that the CPU implements.

	.intel_syntax noprefix 	.text .m0: .string "CPUID: %x\n" .m1: .string "Largest basic function number implemented: %i\n" .m2: .string "Vendor ID: %s\n"      .globl main  main: 	push    r12 	mov	    eax, 1 	sub	    rsp, 16     cpuid     lea	    rdi, .m0[rip] 	mov	    esi, eax 	call	printf 	mov     eax, 0     cpuid 	lea	    rdi, .m1[rip] 	mov	    esi, eax 	mov	    r12d, edx 	mov	    ebp, ecx 	call    printf 	mov     3[rsp], ebx 	lea	    rsi, 3[rsp]     lea	    rdi, .m2[rip]     mov     7[rsp], r12d     mov     11[rsp], ebp 	call	printf 	add	    rsp, 16 	pop	    r12 	ret      .section .note.GNU-stack,"",@progbits 

On some processors, it is possible to modify the Manufacturer ID string reported by CPUID.(EAX=0) by writing a new ID string to particular MSRs (Model-specific registers) using the WRMSR instruction. This has been used on non-Intel processors to enable features and optimizations that have been disabled in software for CPUs that don't return the GenuineIntel ID string.[19] Processors that are known to possess such MSRs include:

Processors with Manufacturer ID MSRs
Processor MSRs
IDT WinChip 108h-109h[20]
VIA C3, C7 1108h-1109h[21]
VIA Nano 1206h-1207h[22]
Transmeta Crusoe, Efficeon 80860001h-80860003h[23][24]
AMD Geode GX, LX 3000h-3001h[25]
DM&P Vortex86EX2 52444300h-52444301h[26]

EAX=1: Processor Info and Feature Bits[edit]

This returns the CPU's stepping, model, and family information in register EAX (also called the signature of a CPU), feature flags in registers EDX and ECX, and additional feature info in register EBX.[27]

CPUID EAX=1: Processor Version Information in EAX
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Reserved Extended Family ID Extended Model ID Reserved Processor Type Family ID Model Stepping ID
  • Stepping ID is a product revision number assigned due to fixed errata or other changes.
  • The actual processor model is derived from the Model, Extended Model ID and Family ID fields. If the Family ID field is either 6 or 15, the model is equal to the sum of the Extended Model ID field shifted left by 4 bits and the Model field. Otherwise, the model is equal to the value of the Model field.
  • The actual processor family is derived from the Family ID and Extended Family ID fields. If the Family ID field is equal to 15, the family is equal to the sum of the Extended Family ID and the Family ID fields. Otherwise, the family is equal to the value of the Family ID field.
  • The meaning of the Processor Type field is given in the table below.
Processor Type
Type Encoding in Binary
Original equipment manufacturer (OEM) Processor 00
Intel Overdrive Processor 01
Dual processor (applicable to Intel P5 Pentium processors only)[28] 10
Reserved value 11

As of October 2023, the following x86 processor family IDs are known:[29]

CPUID EAX=1: Processor Family IDs
Family ID +
Extended Family ID
Intel AMD Other
3h [a]
4h 486 486,[30]
Élan SC4xx/5xx[31]
Cyrix 5x86,[32]
Cyrix MediaGX,[33]
UMC Green CPU,[4]
MCST Elbrus (most models),[10]
MiSTer ao486[34]
5h Pentium,
Pentium MMX,
Quark X1000
Cyrix 6x86,
Cyrix MediaGXm,[33]
Geode (except NX),
NexGen Nx586,[4]
IDT WinChip,
IDT WinChip 2,
IDT WinChip 3,
Transmeta Crusoe,
Rise mP6,
SiS 550,
DM&P Vortex86 (early),[35]
RDC IAD 100,
MCST Elbrus-8C2[10]
6h Pentium Pro,
Pentium II,
Pentium III,
Pentium M,
Intel Core (all variants),
Intel Atom (all variants),
Xeon (except NetBurst variants),
Xeon Phi (except KNC)
K7: Athlon,
Athlon XP
Cyrix 6x86MX/MII,
VIA Nano,
DM&P Vortex86 (DX3,EX2[36]),
Zhaoxin ZX-A/B/C/C+,
(Centaur CNS[37]),
MCST Elbrus-12C/16C/2C3[10]
7h Itanium
(in IA-32 mode)
Zhaoxin KaiXian,
Zhaoxin KaisHeng
8h [b]
0Bh Xeon Phi (Knights Corner)[39]
0Fh NetBurst (Pentium 4) K8/Hammer
(Athlon 64)
Transmeta Efficeon
10h K10: Phenom
11h Itanium 2[40]
(in IA-32 mode)
Turion X2
12h Llano
14h Bobcat
15h Bulldozer,
16h Jaguar,
17h Zen 1,
Zen 2
18h Hygon Dhyana
19h Zen 3,
Zen 4
1Ah (Zen 5)
  1. ^ The i386 processor does not support the CPUID instruction - it does however return Family ID 3h in the reset-value of EDX.
  2. ^ Family ID 8h has been reported to have been deliberately avoided for the Pentium 4 processor family due to incompatibility with Windows NT 4.0.[38]
CPUID EAX=1: Additional Information in EBX
Bits EBX Valid
7:0 Brand Index
15:8 CLFLUSH line size (Value * 8 = cache line size in bytes) if CLFLUSH feature flag is set.

CPUID.01.EDX.CLFSH [bit 19]= 1

23:16 Maximum number of addressable IDs for logical processors in this physical package;

The nearest power-of-2 integer that is not smaller than this value is the number of unique initial APIC IDs reserved for addressing different logical processors in a physical package.[a]

Former use: Number of logical processors per physical processor; two for the Pentium 4 processor with Hyper-Threading Technology.[43]

if Hyper-threading feature flag is set.

CPUID.01.EDX.HTT [bit 28]= 1

31:24 Local APIC ID: The initial APIC-ID is used to identify the executing logical processor.[b] Pentium 4 and subsequent processors.
  1. ^ On CPUs with more than 128 logical processors in a single package (e.g. Intel Xeon Phi 7290[41] and AMD Threadripper Pro 7995WX[42]) the value in bit 23:16 is set to a non-power-of-2 value.
  2. ^ The Local APIC ID can also be identified via the cpuid 0Bh leaf ( CPUID.0Bh.EDX[x2APIC-ID] ). On CPUs with more than 256 logical processors in one package (e.g. Xeon Phi 7290), leaf 0Bh must be used because the APIC ID does not fit into 8 bits.

The processor info and feature flags are manufacturer specific but usually, the Intel values are used by other manufacturers for the sake of compatibility.

CPUID EAX=1: Feature Information in EDX and ECX
Bit Short Feature Short Feature Bit
0 fpu Onboard x87 FPU sse3 SSE3 (Prescott New Instructions - PNI) 0
1 vme Virtual 8086 mode extensions (such as VIF, VIP, PVI) pclmulqdq PCLMULQDQ (carry-less multiply) instruction 1
2 de Debugging extensions (CR4 bit 3) dtes64 64-bit debug store (edx bit 21) 2
3 pse Page Size Extension (4 MB pages) monitor MONITOR and MWAIT instructions (PNI) 3
4 tsc Time Stamp Counter and RDTSC instruction ds-cpl CPL qualified debug store 4
5 msr Model-specific registers and RDMSR/WRMSR instructions vmx Virtual Machine eXtensions 5
6 pae Physical Address Extension smx Safer Mode Extensions (LaGrande) (GETSEC instruction) 6
7 mce Machine Check Exception est Enhanced SpeedStep 7
8 cx8[b] CMPXCHG8B (compare-and-swap) instruction tm2 Thermal Monitor 2 8
9 apic[c] Onboard Advanced Programmable Interrupt Controller ssse3 Supplemental SSE3 instructions 9
10 (mtrr)[d] (reserved) cnxt-id L1 Context ID 10
11 sep[e] SYSENTER and SYSEXIT fast system call instructions sdbg Silicon Debug interface 11
12 mtrr Memory Type Range Registers fma Fused multiply-add (FMA3) 12
13 pge Page Global Enable bit in CR4 cx16 CMPXCHG16B instruction 13
14 mca Machine check architecture xtpr Can disable sending task priority messages 14
15 cmov Conditional move: CMOV, FCMOV and FCOMI instructions[f] pdcm Perfmon & debug capability 15
16 pat Page Attribute Table (reserved)[g] 16
17 pse-36 36-bit page size extension pcid Process context identifiers (CR4 bit 17) 17
18 psn Processor Serial Number supported and enabled[h] dca Direct cache access for DMA writes[51][52] 18
19 clfsh CLFLUSH cache line flush instruction (SSE2) sse4.1 SSE4.1 instructions 19
20 (nx) No-execute (NX) bit (Itanium only)[53][i] sse4.2 SSE4.2 instructions 20
21 ds Debug store: save trace of executed jumps x2apic x2APIC (enhanced APIC) 21
22 acpi Onboard thermal control MSRs for ACPI movbe MOVBE instruction (big-endian) 22
23 mmx MMX instructions (64-bit SIMD) popcnt POPCNT instruction 23
24 fxsr FXSAVE, FXRSTOR instructions, CR4 bit 9 tsc-deadline APIC implements one-shot operation using a TSC deadline value 24
25 sse Streaming SIMD Extensions (SSE) instructions
(aka "Katmai New Instructions"; 128-bit SIMD)
aes-ni AES instruction set 25
26 sse2 SSE2 instructions xsave Extensible processor state save/restore:
27 ss CPU cache implements self-snoop osxsave XSAVE enabled by OS 27
28 htt Max APIC IDs reserved field is Valid[j] avx Advanced Vector Extensions (256-bit SIMD) 28
29 tm Thermal monitor automatically limits temperature f16c Floating-point conversion instructions to/from FP16 format 29
30 ia64 IA64 processor emulating x86[53] rdrnd RDRAND (on-chip random number generator) feature 30
31 pbe Pending Break Enable (PBE# pin) wakeup capability hypervisor Hypervisor present (always zero on physical CPUs)[56][57][58] 31
  1. ^ On some older processors, executing CPUID with a leaf index (EAX) greater than 0 may leave EBX and ECX unmodified, keeping their old values. For this reason, it is recommended to zero out EBX and ECX before executing CPUID with a leaf index of 1.

    Processors noted to exhibit this behavior include Cyrix MII[44] and IDT WinChip 2.[45]

  2. ^ On processors from IDT, Transmeta and Rise (vendor IDs CentaurHauls, GenuineTMx86 and RiseRiseRise), the CMPXCHG8B instruction is always supported, however the feature bit for the instruction might not be set. This is a workaround for a bug in Windows NT.[46]
  3. ^ On early AMD K5 (AuthenticAMD Family 5 Model 0) processors only, EDX bit 9 used to indicate support for PGE instead. This was moved to bit 13 from K5 Model 1 onwards.[47]
  4. ^ Intel AP-485, revisions 006[48] to 008, lists CPUID.(EAX=1):EDX[bit 10] as having the name "MTRR" (albeit described as "Reserved"/"Do not count on their value") - this name was removed in later revisions of AP-485, and the bit has been listed as reserved with no name since then.
  5. ^ On Pentium Pro (GenuineIntel Family 6 Model 1) processors only, EDX bit 11 is invalid - the bit is set, but the SYSENTER and SYSEXIT instructions are not supported on the Pentium Pro.[49]
  6. ^ FCMOV and FCOMI instructions only available if onboard x87 FPU also present (indicated by EDX bit 0).
  7. ^ ECX bit 16 is listed as "Reserved" in public Intel and AMD documentation and is not set in any known processor. However, some versions of the Windows Vista kernel are reported to be checking this bit[50] - if it is set, Vista will recognize it as a "processor channels" feature.
  8. ^ On Intel and Transmeta[23] CPUs that support PSN (Processor Serial Number), the PSN can be disabled by setting bit 21 of MSR 119h (BBL_CR_CTL) to 1. Doing so will remove leaf 3 and cause CPUID.(EAX=1):EDX[bit 18] to return 0.
  9. ^ On non-Itanium x86 processors, support for the No-execute bit is indicated in CPUID.(EAX=8000_0001):EDX[bit 20] instead.
  10. ^ EDX bit 28, if set, indicates that bits 23:16 of CPUID.(EAX=1):EBX are valid. If this bit is not set, then the CPU package contains only 1 logical processor.

    In older documentation, this bit is often listed as a "Hyper-threading technology"[54] flag - however, while this flag is a prerequisite for Hyper-Threading support, it does not by itself indicate support for Hyper-Threading and it has been set on many CPUs that do not feature any form of multi-threading technology.[55]

Reserved fields should be masked before using them for processor identification purposes.

EAX=2: Cache and TLB Descriptor information[edit]

This returns a list of descriptors indicating cache and TLB capabilities in EAX, EBX, ECX and EDX registers.

On processors that support this leaf, calling CPUID with EAX=2 will cause the bottom byte of EAX to be set to 01h[a] and the remaining 15 bytes of EAX/EBX/ECX/EDX to be filled with 15 descriptors, one byte each. These descriptors provide information about the processor's caches, TLBs and prefetch. This is typically one cache or TLB per descriptor, but some descriptor-values provide other information as well - in particular, 00h is used for an empty descriptor, FFh indicates that the leaf does not contain valid cache information and that leaf 4h should be used instead, and FEh indicates that the leaf does not contain valid TLB information and that leaf 18h should be used instead. The descriptors may appear in any order.

For each of the four registers (EAX,EBX,ECX,EDX), if bit 31 is set, then the register should not be considered to contain valid descriptors (e.g. on Itanium in IA-32 mode, CPUID(EAX=2) returns 80000000h in EDX - this should be interpreted to mean that EDX contains no valid information, not that it contains a 512K L2 cache.)

The table below provides, for known descriptor values, a condensed description of the cache or TLB indicated by that descriptor value (or other information, where that applies). The suffixes used in the table are:

  • K,M,G : binary kilobyte, megabyte, gigabyte (capacity for caches, page-size for TLBs)
  • E : entries (for TLBs; e.g. 64E = 64 entries)
  • p : page-size (e.g. 4Kp for TLBs where each entry describes one 4 KB page, 4K/2Mp for TLBs where each entry can describe either one 4 KB page or one 2 MB hugepage)
  • L : cache-line size (e.g. 32L = 32-byte cache line size)
  • S : cache sector size (e.g. 2S means that the cache uses sectors of 2 cache-lines each)
  • A : associativity (e.g. 6A = 6-way set-associative, FA = fully-associative)
Legend for cache/TLB descriptor byte encodings
or data cache
or data TLB
CPUID EAX=2: Cache/TLB descriptor byte encodings
x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF
0x null
ITLB: 32E,
4Kp, 4A
4Mp, FA
DTLB: 64E,
4Kp, 4A
4Mp, 4A
DTLB: 32E,
4Mp, 4A
L1I: 8K,
4A, 32L
0x L1I: 16K,
4A, 32L
L1I: 32K,
4A, 64L
L1D: 8K,
2A, 32L
4Mp, FA
L1D: 16K,
4A, 32L
L1D: 16K,
4A, 64L
L1D: 24K,
6A, 64L
1x (L1D: 16K,
4A, 32L)[b]
(L1I: 16K,
4A, 32L)[b]
1x (L2C: 96K,
6A, 64L)[b]
L2C: 128K,
2A, 64L
2x L2C: 256K,
8A, 64L
L3C: 512K,
4A, 64L, 2S
L3C: 1M,
8A, 64L, 2S
L2C: 1M,
16A, 64L
L3C: 2M,
8A, 64L, 2S
2x (128-byte
L3C: 4M,
8A, 64L, 2S
L1D: 32K,
8A, 64L
3x L1I: 32K,
8A, 64L
3x L2C: 128K,
4A, 64L, 2S[d]
L2C: 192K,
6A, 64L, 2S[d]
L2C: 128K,
2A, 64L, 2S[d]
L2C: 256K,
4A, 64L, 2S[d]
L2C: 384K,
6A, 64L, 2S[d]
L2C: 512K,
4A, 64L, 2S[d]
4x no L3 cache
L2C: 128K,
4A, 32L
L2C: 256K,
4A, 32L
L2C: 512K,
4A, 32L
L2C: 1M,
4A, 32L
L2C: 2M,
4A, 32L
L3C: 4M,
4A, 64L
L3C: 8M,
8A, 64L
4x L2C: 3M,
12A, 64L
4M, 16A, 64L
L3C: 6M,
12A, 64L
L3C: 8M,
16A, 64L
L3C: 12M,
12A, 64L
L3C: 16M,
16A, 64L
L2C: 6M,
24A, 64L
ITLB: 32E,
5x ITLB: 64E,FA,
ITLB: 128E,FA,
ITLB: 256E,FA,
2M/4Mp, FA
DTLB: 16E,
4Mp, 4A
DTLB: 16E,
4Kp, 4A
5x DTLB: 16E,
4Kp, FA
DTLB: 32E,
2M/4Mp, 4A
4K/4Mp, FA
DTLB: 128E,
4K/4Mp, FA
DTLB: 256E,
4K/4Mp, FA
6x L1D: 16K,
8A, 64L
ITLB: 48E,
4Kp, FA
Two DTLBs:
32E, 2M/4Mp, 4A
+ 4E, 1Gp, FA
DTLB: 512E,
4Kp, 4A
L1D: 8K,
4A, 64L
L1D: 16K,
4A, 64L
6x L1D: 32K,
4A, 64L
DTLB: 64E,
4Kp, 8A
DTLB: 256E,
4Kp, 8A
DTLB: 128E,
2M/4Mp, 8A
DTLB: 16E,
1Gp, FA
7x Trace cache,
12K-μop, 8A[g]
Trace cache,
16K-μop, 8A
Trace cache,
32K-μop, 8A
Trace cache,
64K-μop, 8A[d]
2M/4Mp, FA[h]
(L1I: 16K,
4A, 64L)[i]
7x L2C: 1M,
4A, 64L
L2C: 128K,
8A, 64L, 2S
L2C: 256K,
8A, 64L, 2S
L2C: 512K,
8A, 64L, 2S
L2C: 1M,
8A, 64L, 2S
L2C: 2M,
8A, 64L
(L2C: 256K,
8A, 128L)[i]
L2C: 512K,
2A, 64L
8x L2C: 512K,
8A, 64L[g]
(L2C: 128K,
8A, 32L)[c]
L2C: 256K,
8A, 32L
L2C: 512K,
8A, 32L
L2C: 1M,
8A, 32L
L2C: 2M,
8A, 32L
L2C: 512K,
4A, 64L
L2C: 1M,
8A, 64L
8x (L3C: 2M,
4A, 64L)[b]
(L3C: 4M,
4A, 64L)[b]
(L3C: 8M,
4A, 64L)[b]
(L3C: 3M,
12A, 128L)[i][j]
9x (ITLB: 64E,FA,
(DTLB: 32E,FA,
9x (DTLB: 96E,FA,
Ax DTLB: 32E,
4Kp, FA
Ax Ax
Bx ITLB: 128E,
4Kp, 4A
2M/4Mp, 4A[k]
ITLB: 64E,
4Kp, 4A
DTLB: 128E,
4Kp, 4A
DTLB: 256E,
4Kp, 4A
ITLB: 64E,
4Kp, 8A
ITLB: 128E,
4Kp, 8A
Bx DTLB: 64E,
4Kp, 4A
Cx DTLB: 8E,
4K/4Mp, 4A
L2TLB: 1024E,
4K/2Mp, 8A
DTLB: 16E,
2M/4Mp, 4A[70]
Two L2 STLBs:
1536E, 4K/2Mp, 6A
+ 16E, 1Gp, 4A
DTLB: 32E,
2M/4Mp, 4A
Cx L2TLB: 512E,
4Kp, 4A
Dx L3C: 512K,
4A, 64L
L3C: 1M,
4A, 64L
L3C: 2M,
4A, 64L
L3C: 1M,
8A, 64L
L3C: 2M,
8A, 64L
Dx L3C: 4M,
8A, 64L
L3C: 1.5M,
12A, 64L
L3C: 3M,
12A, 64L
L3C: 6M,
12A, 64L
Ex L3C: 2M,
16A, 64L
L3C: 4M,
16A, 64L
L3C: 8M,
16A, 64L
Ex L3C: 12M,
24A, 64L
L3C: 18M,
24A, 64L[71]
L3C: 24M,
24A, 64L
Fx 64-byte
Fx Leaf 2 has
no TLB info,
use leaf 18h
Leaf 2 has
no cache info,
use leaf 4
x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF
  1. ^ In older Intel documentation, the bottom byte of the value returned in EAX is described as specifying the number of times the CPUID must be called with EAX=2 to get hold of all the cache/TLB descriptors. However, all known processors that implement this leaf return 01h in this byte, and newer Intel documentation (SDM rev 053[59] and later) specifies this byte as having the value 01h.
  2. ^ a b c d e f g h i Descriptors 10h, 15h, 1Ah, 88h, 89h, 8Ah, 90h, 96h, 9Bh are documented for the IA-32 operation mode of Itanium only.[60]
  3. ^ a b c d Descriptor values 26h,27h,28h and 81h are not listed in Intel documentation and are not used in any known CPU, but have been reported to be recognized by the Windows NT kernel v5.1 (Windows XP) and higher. 81h is also recognized by v5.0 (Windows 2000).[67]
  4. ^ a b c d e f g Descriptors 39h-3Eh and 73h are listed in rev 36 of Intel AP-485,[61] but have been removed from later Intel documentation even though some of them have been used in Intel CPUs (e.g. 39h in "Willamette-128"-based Celeron processors[62]).
  5. ^ Descriptor 49h indicates a level-3 cache on GenuineIntel Family 0Fh Model 6 (Pentium 4 based Xeon) CPUs, and a level-2 cache on other CPUs.
  6. ^ Intel's CPUID documentation does not specify the associativity of the ITLB indicated by descriptor 4Fh. The processors that use this descriptor (Intel Atom "Bonnell"[63]) are listed elsewhere as having a fully-associative 32-entry ITLB.[64]
  7. ^ a b On Cyrix and Geode CPUs (Vendor IDs CyrixInstead and Geode by NSC), descriptors 70h and 80h have a different meaning:[65]
    • Descriptor 70h indicates a 32-entry shared instruction+data 4-way-set-associative TLB with a 4K page size.
    • Descriptor 80h indicates a 16 KB shared instruction+data L1 cache with 4-way set-associativity and a cache-line size of 16 bytes.
  8. ^ Descriptor 76h is listed as an 1 MB L2 cache in rev 37 of Intel AP-485,[66] but as an instruction TLB in rev 38 and all later Intel documentation.
  9. ^ a b c Descriptors 77h, 7Eh, 8Dh are documented for the IA-32 operation mode of Itanium 2 only.[68]
  10. ^ Under the IA-32 operation mode of Itanium 2, the L3 cache size is always reported as 3 MB regardless of the actual size of the cache.[69]
  11. ^ For descriptor B1h, the TLB capacity is 8 elements when using 2 MB pages, but reduced to 4 elements when using 4 MB pages.
  12. ^ a b The prefetch specified by descriptors F0h and F1h is the recommended stride for memory prefetching with the PREFETCHNTA instruction.[72]

EAX=3: Processor Serial Number[edit]

This returns the processor's serial number. The processor serial number was introduced on Intel Pentium III, but due to privacy concerns, this feature is no longer implemented on later models (the PSN feature bit is always cleared). Transmeta's Efficeon and Crusoe processors also provide this feature. AMD CPUs however, do not implement this feature in any CPU models.

For Intel Pentium III CPUs, the serial number is returned in the EDX:ECX registers. For Transmeta Efficeon CPUs, it is returned in the EBX:EAX registers. And for Transmeta Crusoe CPUs, it is returned in the EBX register only.

Note that the processor serial number feature must be enabled in the BIOS setting in order to function.

EAX=4 and EAX=8000001Dh: Cache hierarchy and topology[edit]

These two leaves are used to provide information about the cache hierarchy levels available to the processor core on which the CPUID instruction is run. Leaf 4 is used on Intel processors and leaf 8000001Dh is used on AMD processors - they both return data in EAX, EBX, ECX and EDX, using the same data format except that leaf 4 returns a few additional fields that are considered "reserved" for leaf 8000001Dh. They both provide CPU cache information in a series of sub-leaves selected by ECX - to get information about all the cache levels, it is necessary to invoke CPUID repeatedly, with EAX=4 or 8000001Dh and ECX set to increasing values starting from 0 (0,1,2,...) until a sub-leaf not describing any caches (EAX[4:0]=0) is found. The sub-leaves that do return cache information may appear in any order, but all of them will appear before the first sub-leaf not describing any caches.

In the below table, fields that are defined for leaf 4 but not for leaf 8000001Dh are highlighted with yellow cell coloring and a (#4) item.

CPUID EAX=4 and 8000001Dh: Cache property information in EAX, EBX and EDX
0 Cache Type:
  • 0: (No more caches)
  • 1: Data Cache
  • 2: Instruction Cache
  • 3: Unified Cache
  • 4-31: (reserved)
System coherency line size in bytes, minus 1 WBINVD cache invalidation execution scope.
A value of 0 indicates that the INVD/WBINVD instructions will invalidate all lower-levels caches of this cache, including caches that belong to sibling processors sharing this cache. A value of 1 indicates that lower-level caches of sibling processors that are sharing this cache are not guaranteed to be all cleared.
1 Cache inclusiveness. If 1, then cache is inclusive of lower-level caches. 1
2 Complex cache indexing. If 1, then cache uses a complex function for cache indexing, else the cache is direct-mapped. (#4) 2
3 (reserved) 3
4 (reserved) 4
7:5 Cache Level (starting from 1) (reserved) 7:5
8 Self initializing cache level (1=doesn't need software initialization after reset) (reserved) 8
9 Fully Associative Cache (reserved) 9
10 (WBINVD cache invalidation execution scope)[a] (#4) (reserved) 10
11 (Cache Inclusiveness)[a] (#4) (reserved) 11
13:12 (reserved) Physical line partitions (number of cache lines that share a cache address tag), minus 1 (reserved) 13:12
21:14 Maximum number of addressable IDs for logical processors sharing this cache, minus 1 (reserved) 21:14
25:22 Ways of cache associativity, minus 1 (reserved) 25:22
31:26 Maximum number of addressable IDs for processor cores in physical package, minus 1 (#4) (reserved) 31:26
  1. ^ a b For CPUID leaf 4, bits 11:10 of EAX are documented for the Xeon Phi "Knights Corner" (GenuineIntel Family 0Bh) processor only.[39] For other processors, bits 1:0 of EDX should be used instead.

For any caches that are valid and not fully-associative, the value returned in ECX is the number of sets in the cache minus 1. (For fully-associative caches, ECX should be treated as if it return the value 0.) For any given cache described by a sub-leaf of CPUID leaf 4 or 8000001Dh, the total cache size in bytes can be computed as:
CacheSize = (EBX[11:0]+1) * (EBX[21:12]+1) * (EBX[31:22]+1) * (ECX+1)

EAX=4 and EAX=Bh: Intel thread/core and cache topology[edit]

These two leaves are used for processor topology (thread, core, package) and cache hierarchy enumeration in Intel multi-core (and hyperthreaded) processors.[73] As of 2013 AMD does not use these leaves but has alternate ways of doing the core enumeration.[74]

Unlike most other CPUID leaves, leaf Bh will return different values in EDX depending on which logical processor the CPUID instruction runs; the value returned in EDX is actually the x2APIC id of the logical processor. The x2APIC id space is not continuously mapped to logical processors, however; there can be gaps in the mapping, meaning that some intermediate x2APIC ids don't necessarily correspond to any logical processor. Additional information for mapping the x2APIC ids to cores is provided in the other registers. Although the leaf Bh has sub-leaves (selected by ECX as described further below), the value returned in EDX is only affected by the logical processor on which the instruction is running but not by the subleaf.

The processor(s) topology exposed by leaf Bh is a hierarchical one, but with the strange caveat that the order of (logical) levels in this hierarchy doesn't necessarily correspond to the order in the physical hierarchy (SMT/core/package). However, every logical level can be queried as an ECX subleaf (of the Bh leaf) for its correspondence to a "level type", which can be either SMT, core, or "invalid". The level id space starts at 0 and is continuous, meaning that if a level id is invalid, all higher level ids will also be invalid. The level type is returned in bits 15:08 of ECX, while the number of logical processors at the level queried is returned in EBX. Finally, the connection between these levels and x2APIC ids is returned in EAX[4:0] as the number of bits that the x2APIC id must be shifted in order to obtain a unique id at the next level.

As an example, a dual-core Westmere processor capable of hyperthreading (thus having two cores and four threads in total) could have x2APIC ids 0, 1, 4 and 5 for its four logical processors. Leaf Bh (=EAX), subleaf 0 (=ECX) of CPUID could for instance return 100h in ECX, meaning that level 0 describes the SMT (hyperthreading) layer, and return 2 in EBX because there are two logical processors (SMT units) per physical core. The value returned in EAX for this 0-subleaf should be 1 in this case, because shifting the aforementioned x2APIC ids to the right by one bit gives a unique core number (at the next level of the level id hierarchy) and erases the SMT id bit inside each core. A simpler way to interpret this information is that the last bit (bit number 0) of the x2APIC id identifies the SMT/hyperthreading unit inside each core in our example. Advancing to subleaf 1 (by making another call to CPUID with EAX=Bh and ECX=1) could for instance return 201h in ECX, meaning that this is a core-type level, and 4 in EBX because there are 4 logical processors in the package; EAX returned could be any value greater than 3, because it so happens that bit number 2 is used to identify the core in the x2APIC id. Note that bit number 1 of the x2APIC id is not used in this example. However, EAX returned at this level could well be 4 (and it happens to be so on a Clarkdale Core i3 5x0) because that also gives a unique id at the package level (=0 obviously) when shifting the x2APIC id by 4 bits. Finally, you may wonder what the EAX=4 leaf can tell us that we didn't find out already. In EAX[31:26] it returns the APIC mask bits reserved for a package; that would be 111b in our example because bits 0 to 2 are used for identifying logical processors inside this package, but bit 1 is also reserved although not used as part of the logical processor identification scheme. In other words, APIC ids 0 to 7 are reserved for the package, even though half of these values don't map to a logical processor.

The cache hierarchy of the processor is explored by looking at the sub-leaves of leaf 4. The APIC ids are also used in this hierarchy to convey information about how the different levels of cache are shared by the SMT units and cores. To continue our example, the L2 cache, which is shared by SMT units of the same core but not between physical cores on the Westmere is indicated by EAX[26:14] being set to 1, while the information that the L3 cache is shared by the whole package is indicated by setting those bits to (at least) 111b. The cache details, including cache type, size, and associativity are communicated via the other registers on leaf 4.

Beware that older versions of the Intel app note 485 contain some misleading information, particularly with respect to identifying and counting cores in a multi-core processor;[75] errors from misinterpreting this information have even been incorporated in the Microsoft sample code for using CPUID, even for the 2013 edition of Visual Studio,[76] and also in the sandpile.org page for CPUID,[77] but the Intel code sample for identifying processor topology[73] has the correct interpretation, and the current Intel Software Developer's Manual has a more clear language. The (open source) cross-platform production code[78] from Wildfire Games also implements the correct interpretation of the Intel documentation.

Topology detection examples involving older (pre-2010) Intel processors that lack x2APIC (thus don't implement the EAX=Bh leaf) are given in a 2010 Intel presentation.[79] Beware that using that older detection method on 2010 and newer Intel processors may overestimate the number of cores and logical processors because the old detection method assumes there are no gaps in the APIC id space, and this assumption is violated by some newer processors (starting with the Core i3 5x0 series), but these newer processors also come with an x2APIC, so their topology can be correctly determined using the EAX=Bh leaf method.

EAX=5: MONITOR/MWAIT Features[edit]

This returns feature information related to the MONITOR and MWAIT instructions in the EAX, EBX, ECX and EDX registers.

CPUID EAX=5: MONITOR/MWAIT feature information in EAX, EBX, EDX
3:0 Smallest monitor-line size in bytes Largest monitor-line size in bytes Number of C0[a] sub-states supported for MWAIT 3:0
7:4 Number of C1 sub-states supported for MWAIT 7:4
11:8 Number of C2 sub-states supported for MWAIT 11:8
15:12 Number of C3 sub-states supported for MWAIT 15:12
19:16 (reserved) (reserved) Number of C4 sub-states supported for MWAIT 19:16
23:20 Number of C5 sub-states supported for MWAIT 23:20
27:24 Number of C6 sub-states supported for MWAIT 27:24
31:28 Number of C7 sub-states supported for MWAIT 31:28
  1. ^ The C0 to C7 states are processor-specific C-states, which do not necessarily correspond 1:1 to ACPI C-states.
CPUID EAX=5: MONITOR/MWAIT extension enumeration in ECX
Short Feature
0 EMX Enumeration of MONITOR/MWAIT extensions in ECX and EDX supported
1 IBE Supports treating interrupts as break-events for MWAIT even when interrupts are disabled
2 (reserved)
3 Monitorless_­MWAIT Allow MWAIT to be used for power management without setting up memory monitoring with MONITOR[80]


EAX=6: Thermal and power management[edit]

This returns feature bits in the EAX register and additional information in the EBX, ECX and EDX registers.

CPUID EAX=6: Thermal/power management feature bits in EAX
Short Feature
0 DTS Digital Thermal Sensor capability
1 Intel Turbo Boost Technology capability
2 ARAT[a] Always Running APIC Timer capability
3 (reserved)
4 PLN Power Limit Notification capability
5 ECMD Extended Clock Modulation Duty capability
6 PTM Package Thermal Management capability
7 HWP Hardware-controlled Performance States. MSRs added:
  • IA32_PM_ENABLE(770h)
  • IA32_HWP_REQUEST(774h)
  • IA32_HWP_STATUS(777h
8 HWP_Notification HWP notification of dynamic guaranteed performance change - IA32_HWP_INTERRUPT(773h) MSR
9 HWP_Activity_­Window HWP Activity Window control - bits 41:32 of IA32_HWP_REQUEST MSR
10 HWP_Energy_­Performance_­Preference HWP Energy/performance preference control - bits 31:24 of IA32_HWP_REQUEST MSR
11 HWP_Package_­Level_Request HWP Package-level control - IA32_HWP_REQUEST_PKG(772h) MSR
12 (reserved)
13 HDC Hardware Duty Cycling supported. MSRs added:
  • IA32_PKG_HDC_CTL (DB0h)
  • IA32_PM_CTL1 (DB1h)
14 Intel Turbo Boost Max Technology 3.0 available
15 Interrupts upon changes to IA32_HWP_CAPABILITIES.Highest_Performance (bits 7:0) supported
16 HWP PECI override supported - bits 63:60 of IA32_HWP_PECI_REQUEST_INFO(775h) MSR
17 Flexible HWP - bits 63:59 of IA32_HWP_REQUEST MSR
18 Fast access mode for IA32_HWP_REQUEST MSR supported[b]
19 HW_FEEDBACK Hardware Feedback Interface. Added MSRs:
  • IA32_HW_FEEDBACK_CONFIG(17D1h) (bit 0 enables HFI, bit 1 enables Intel Thread Director)
20 IA32_HWP_REQUEST of idle logical processor ignored when only one of two logical processors that share a physical processor is active.
21 (reserved)
22 IA32_HWP_CTL(776h) MSR supported[82]
23 Intel Thread Director supported. Added MSRs:
24 IA32_THERM_INTERRUPT MSR bit 25 supported

  1. ^ On Intel Pentium 4 family processors only, bit 2 of EAX is used to indicate OPP (Operating Point Protection)[81] instead of ARAT.
  2. ^ To enable fast (non-serializing) access mode for the IA32_HWP_REQUEST MSR on CPUs that support it, it is necessary to set bit 0 of the FAST_UNCORE_MSRS_CTL(657h) MSR.
CPUID EAX=6: Thermal/power management feature fields in EBX, ECX and EDX
0 Number of Interrupt Thresholds in Digital Thermal Sensor Effective frequency interface supported - IA32_MPERF(0E7h) and IA32_APERF(0E8h) MSRs Hardware Feedback reporting: Performance Capability Reporting supported 0
1 (ACNT2 Capability)[a] Hardware Feedback reporting: Efficiency Capability Reporting supported 1
2 (reserved) (reserved) 2
3 Performance-Energy Bias capability - IA32_ENERGY_PERF_BIAS(1B0h) MSR 3
7:4 (reserved) (reserved) 7:4
11:8 Number of Intel Thread Director classes supported by hardware Size of Hardware Feedback interface structure (in units of 4 KB) minus 1 11:8
15:12 (reserved) 15:12

(reserved) Index of this logical processor's row in hardware feedback interface structure
  1. ^ The "ACNT2 Capability" bit is listed in Intel AP-485 rev 038[83] and 039, but not listed in any revision of the Intel SDM. The feature is known to exist in only a few Intel CPUs, e.g. Xeon "Harpertown" stepping E0.[84]

EAX=7, ECX=0: Extended Features[edit]

This returns extended feature flags in EBX, ECX, and EDX. Returns the maximum ECX value for EAX=7 in EAX.

CPUID EAX=7,ECX=0: Extended feature bits in EBX, ECX and EDX
Short Feature Short Feature Short Feature
0 fsgsbase Access to base of %fs and %gs prefetchwt1 PREFETCHWT1 instruction (sgx-tem)[a] ? 0
1 IA32_TSC_ADJUST MSR avx512-vbmi AVX-512 Vector Bit Manipulation Instructions sgx-keys Attestation Services for Intel SGX 1
2 sgx Software Guard Extensions umip User-mode Instruction Prevention avx512-4vnniw AVX-512 4-register Neural Network Instructions 2
3 bmi1 Bit Manipulation Instruction Set 1 pku Memory Protection Keys for User-mode pages avx512-4fmaps AVX-512 4-register Multiply Accumulation Single precision 3
4 hle TSX Hardware Lock Elision ospke PKU enabled by OS fsrm Fast Short REP MOVSB 4
5 avx2 Advanced Vector Extensions 2 waitpkg Timed pause and user-level monitor/wait instructions (TPAUSE, UMONITOR, UMWAIT) uintr User Inter-processor Interrupts 5
6 fdp-excptn-only x87 FPU data pointer register updated on exceptions only avx512-vbmi2 AVX-512 Vector Bit Manipulation Instructions 2 (reserved) 6
7 smep Supervisor Mode Execution Prevention cet_ss/shstk Control flow enforcement (CET): shadow stack (SHSTK alternative name) (reserved) 7
8 bmi2 Bit Manipulation Instruction Set 2 gfni Galois Field instructions avx512-vp2intersect AVX-512 vector intersection instructions on 32/64-bit integers 8
9 erms Enhanced REP MOVSB/STOSB vaes Vector AES instruction set (VEX-256/EVEX) srbds-ctrl Special Register Buffer Data Sampling Mitigations 9
10 invpcid INVPCID instruction vpclmulqdq CLMUL instruction set (VEX-256/EVEX) md-clear VERW instruction clears CPU buffers 10
11 rtm TSX Restricted Transactional Memory avx512-vnni AVX-512 Vector Neural Network Instructions rtm-always-abort[85] All TSX transactions are aborted 11
12 rdt-m/pqm Intel Resource Director (RDT) Monitoring or AMD Platform QOS Monitoring avx512-bitalg AVX-512 BITALG instructions (reserved) 12
13 x87 FPU CS and DS deprecated tme_en Total Memory Encryption MSRs available rtm-force-abort[85] TSX_FORCE_ABORT (MSR 0x10f) is available 13
14 mpx Intel MPX (Memory Protection Extensions) avx512-vpopcntdq AVX-512 Vector Population Count Double and Quad-word serialize SERIALIZE instruction 14
15 rdt-a/pqe Intel Resource Director (RDT) Allocation or AMD Platform QOS Enforcement (fzm)[a] ? hybrid Mixture of CPU types in processor topology (e.g. Alder Lake) 15
16 avx512-f AVX-512 Foundation la57 5-level paging (57 address bits) tsxldtrk TSX load address tracking suspend/resume instructions (TSUSLDTRK and TRESLDTRK) 16
17 avx512-dq AVX-512 Doubleword and Quadword Instructions mawau The value of userspace MPX Address-Width Adjust used by the BNDLDX and BNDSTX Intel MPX instructions in 64-bit mode (reserved) 17
18 rdseed RDSEED instruction pconfig Platform configuration (Memory Encryption Technologies Instructions) 18
19 adx Intel ADX (Multi-Precision Add-Carry Instruction Extensions) lbr Architectural Last Branch Records 19
20 smap Supervisor Mode Access Prevention cet-ibt Control flow enforcement (CET): indirect branch tracking 20
21 avx512-ifma AVX-512 Integer Fused Multiply-Add Instructions (reserved) 21
22 (pcommit) (PCOMMIT instruction, deprecated)[87] rdpid RDPID (Read Processor ID) instruction and IA32_TSC_AUX MSR amx-bf16 AMX tile computation on bfloat16 numbers 22
23 clflushopt CLFLUSHOPT instruction kl AES Key Locker avx512-fp16 AVX-512 half-precision floating-point arithmetic instructions[88] 23
24 clwb CLWB (Cache line writeback) instruction bus-lock-detect Bus lock debug exceptions amx-tile AMX tile load/store instructions 24
25 pt Intel Processor Trace cldemote CLDEMOTE (Cache line demote) instruction amx-int8 AMX tile computation on 8-bit integers 25
26 avx512-pf AVX-512 Prefetch Instructions (mprr)[a] ? ibrs / spec_ctrl Speculation Control, part of Indirect Branch Control (IBC):
Indirect Branch Restricted Speculation (IBRS) and
Indirect Branch Prediction Barrier (IBPB)[89][90]
27 avx512-er AVX-512 Exponential and Reciprocal Instructions movdiri MOVDIRI instruction stibp Single Thread Indirect Branch Predictor, part of IBC[89] 27
28 avx512-cd AVX-512 Conflict Detection Instructions movdir64b MOVDIR64B (64-byte direct store) instruction L1D_FLUSH IA32_FLUSH_CMD MSR 28
29 sha SHA-1 and SHA-256 extensions enqcmd Enqueue Stores and EMQCMD/EMQCMDS instructions IA32_ARCH_CAPABILITIES MSR (lists speculative side channel mitigations[89]) 29
30 avx512-bw AVX-512 Byte and Word Instructions sgx-lc SGX Launch Configuration IA32_CORE_CAPABILITIES MSR (lists model-specific core capabilities) 30
31 avx512-vl AVX-512 Vector Length Extensions pks Protection keys for supervisor-mode pages ssbd Speculative Store Bypass Disable,[89] as mitigation for Speculative Store Bypass (IA32_SPEC_CTRL) 31
  1. ^ a b c As of April 2024, the FZM, MPRR and SGX_TEM bits are listed only in Intel TDX documentation[86] and are not set in any known processor.

EAX=7, ECX=1: Extended Features[edit]

This returns extended feature flags in all four registers.

CPUID EAX=7,ECX=1: Extended feature bits in EAX, EBX, ECX, and EDX
Short Feature Short Feature Short Feature Short Feature
0 sha512 SHA-512 extensions Intel PPIN (Protected Processor Inventory Number): IA32_PPIN_CTL (04Eh) and IA32_PPIN (04Fh) MSRs. (reserved) (reserved) 0
1 sm3 SM3 hash extensions pbndkb Total Storage Encryption: PBNDKB instruction and TSE_CAPABILITY (9F1h) MSR. (reserved) (reserved) 1
2 sm4 SM4 cipher extensions (reserved) legacy_reduced_isa X86S (reserved) 2
3 rao-int Remote Atomic Operations on integers: AADD, AAND, AOR, AXOR instructions (reserved) (reserved) (reserved) 3
4 avx-vnni AVX Vector Neural Network Instructions (VNNI) (VEX encoded) (reserved) sipi64 64-bit SIPI avx-vnni-int8 AVX VNNI INT8 instructions 4
5 avx512-bf16 AVX-512 instructions for bfloat16 numbers (reserved) (reserved) avx-ne-convert AVX no-exception FP conversion instructions (bfloat16↔FP32 and FP16→FP32) 5
6 lass Linear Address Space Separation (CR4 bit 27) (reserved) (reserved) (reserved) 6
7 cmpccxadd CMPccXADD instructions (reserved) (reserved) (reserved) 7
8 archperfmonext Architectural Performance Monitoring Extended Leaf (EAX=23h) (reserved) (reserved) amx-complex AMX support for "complex" tiles (TCMMIMFP16PS and TCMMRLFP16PS) 8
9 (dedup)[a] ? (reserved) (reserved) (reserved) 9
10 fzrm Fast zero-length REP MOVSB (reserved) (reserved) avx-vnni-int16 AVX VNNI INT16 instructions 10
11 fsrs Fast short REP STOSB (reserved) (reserved) (reserved) 11
12 rsrcs Fast short REP CMPSB and REP SCASB (reserved) (reserved) (reserved) 12
13 (reserved) (reserved) (reserved) utmr User-timer events: IA32_UINTR_TIMER (1B00h) MSR 13
14 (reserved) (reserved) (reserved) prefetchi Instruction-cache prefetch instructions (PREFETCHIT0 and PREFETCHIT1) 14
15 (reserved) (reserved) (reserved) user_msr User-mode MSR access instructions (URDMSR and UWRMSR) 15
16 (reserved) (reserved) (reserved) (reserved) 16
17 fred Flexible Return and Event Delivery[91] (reserved) (reserved) uiret-uif-from-rflags If 1, the UIRET (User Interrupt Return) instruction will set UIF (User Interrupt Flag) to the value of bit 1 of the RFLAGS image popped off the stack. 17
18 lkgs LKGS Instruction[91] (reserved) (reserved) cet-sss If 1, then Control-Flow Enforcement (CET) Supervisor Shadow Stacks (SSS) are guaranteed not to become prematurely busy as long as shadow stack switching does not cause page faults on the stack being switched to.[92][93] 18
19 wrmsrns WRMSRNS instruction (non-serializing write to MSRs) (reserved) (reserved) avx10 AVX10 Converged Vector ISA (see also leaf 24h)[94] 19
20 nmi_src NMI source reporting[91] (reserved) (reserved) (reserved) 20
21 amx-fp16 AMX instructions for FP16 numbers (reserved) (reserved) APX_F Advanced Performance Extensions, Foundation (adds REX2 and extended EVEX prefix encodings to support 32 GPRs, as well as some new instructions)[95] 21
22 hreset HRESET instruction, IA32_HRESET_ENABLE (17DAh) MSR, and Processor History Reset Leaf (EAX=20h) (reserved) (reserved) (reserved) 22
23 avx-ifma AVX IFMA instructions (reserved) (reserved) mwait MWAIT instruction[b] 23
24 (reserved) (reserved) (reserved) (reserved) 24
25 (reserved) (reserved) (reserved) (reserved) 25
26 lam Linear Address Masking (reserved) (reserved) (reserved) 26
27 msrlist RDMSRLIST and WRMSRLIST instructions, and the IA32_BARRIER (02Fh) MSR (reserved) (reserved) (reserved) 27
28 (reserved) (reserved) (reserved) (reserved) 28
29 (reserved) (reserved) (reserved) (reserved) 29
30 invd_disable_­post_bios_done If 1, supports INVD instruction execution prevention after BIOS Done. (reserved) (reserved) (reserved) 30
31 (reserved) (reserved) (reserved) (reserved) 31
  1. ^ As of April 2024, the DEDUP bit is listed only in Intel TDX documentation[86] and is not set in any known processor.
  2. ^ Support for the MWAIT instruction may be indicated by either CPUID.(EAX=1).ECX[3] or CPUID.(EAX=7,ECX=1).EDX[23]. (One or both may be set.) The former indicates support for the MONITOR instruction as well, while the latter does not indicate one way or another whether the MONITOR instruction is present. MWAIT without MONITOR may be present in systems that support the "Monitorless MWAIT" feature (which is itself indicated by CPUID.(EAX=5).ECX[3].)

EAX=7, ECX=2: Extended Features[edit]

This returns extended feature flags in EDX.

EAX, EBX and ECX are reserved.

CPUID EAX=7,ECX=2: Extended feature bits in EDX
Short Feature
0 psfd Fast Store Forwarding Predictor disable supported. (SPEC_CTRL (MSR 48h) bit 7)
1 ipred_ctrl IPRED_DIS controls[96] supported. (SPEC_CTRL bits 3 and 4)

IPRED_DIS prevents instructions at an indirect branch target from speculatively executing until the branch target address is resolved.

2 rrsba_ctrl RRSBA behavior[97][96] disable supported. (SPEC_CTRL bits 5 and 6)
3 ddpd_u Data Dependent Prefetcher disable supported. (SPEC_CTRL bit 8)
4 bhi_ctrl BHI_DIS_S behavior[96] enable supported. (SPEC_CTRL bit 10)

BHI_DIS_S prevents predicted targets of indirect branches executed in ring0/1/2 from being selected based on branch history from branches executed in ring 3.

5 mcdt_no If set, the processor does not exhibit MXCSR configuration dependent timing.
6 UC-lock disable feature supported.


EAX=0Dh: XSAVE features and state-components[edit]

This leaf is used to enumerate XSAVE features and state-components.

The XSAVE instruction set extension is designed to save/restore CPU extended state (typically for the purpose of context switching) in a manner that can be extended to cover new instruction set extensions without the OS context-switching code needing to understand the specifics of the new extensions. This is done by defining a series of state-components, each with a size and offset within a given save area, and each corresponding to a subset of the state needed for one CPU extension or another. The EAX=0Dh CPUID leaf is used to provide information about which state-components the CPU supports and what their sizes/offsets are, so that the OS can reserve the proper amount of space and set the associated enable-bits.

The state-components can be subdivided into two groups: user-state (state-items that are visible to the application, e.g. AVX-512 vector registers), and supervisor-state (state items that affect the application but are not directly user-visible, e.g. user-mode interrupt configuration). The user-state items are enabled by setting their associated bits in the XCR0 control register, while the supervisor-state items are enabled by setting their associated bits in the IA32_XSS (0DA0h) MSR - the indicated state items then become the state-components that can be saved and restored with the XSAVE/XRSTOR family of instructions.

The XSAVE mechanism can handle up to 63 state-components in this manner. State-components 0 and 1 (x87 and SSE, respectively) have fixed offsets and sizes - for state-components 2 to 62, their sizes, offsets and a few additional flags can be queried by executing CPUID with EAX=0Dh and ECX set to the index of the state-component. This will return the following items in EAX, EBX and ECX (with EDX being reserved):

CPUID EAX=0Dh, ECX≥2: XSAVE state-component information
0 Size in bytes of state-component Offset of state-component from the start of the XSAVE/XRSTOR save area

(This offset is 0 for supervisor state-components, since these can only be saved with the XSAVES/XRSTORS instruction, which use compacting.)

User/supervisor state-component:
  • 0=user-state (enabled through XCR0)
  • 1=supervisor-state (enabled through IA32_XSS)
1 64-byte alignment enable when state save compaction is used.

If this bit is set for a state-component, then, when storing state with compaction, padding will be inserted between the preceding state-component and this state-component as needed to provide 64-byte alignment. If this bit is not set, the state-component will be stored directly after the preceding one.



Attempting to query an unsupported state-component in this manner results in EAX,EBX,ECX and EDX all being set to 0.

Sub-leaves 0 and 1 of CPUID leaf 0Dh are used to provide feature information:

CPUID EAX=0Dh,ECX=0: XSAVE features
Maximum size (in bytes) of XSAVE save area for the set of state-components currently set in XCR0. Maximum size (in bytes) of XSAVE save area if all state-components supported by XCR0 on this CPU were enabled at the same time. 64-bit bitmap of state-components supported by XCR0 on this CPU.
CPUID EAX=0Dh,ECX=1: XSAVE extended features
XSAVE feature flags (see below table) Size (in bytes) of XSAVE area containing all the state-components currently set in XCR0 and IA32_XSS combined. 64-bit bitmap of state-components supported by IA32_XSS on this CPU.
EAX=0Dh,ECX=1: XSAVE feature flags in EAX
Short Feature
0 xsaveopt XSAVEOPT instruction: save state-components that have been modified since last XRSTOR
1 xsavec XSAVEC instruction: save/restore state with compaction
2 xgetbv_ecx1 XGETBV with ECX=1 support
3 xss XSAVES and XRSTORS instructions and IA32_XSS MSR: save/restore state with compaction, including supervisor state.
4 xfd XFD (Extended Feature Disable) supported


As of July 2023, the XSAVE state-components that have been architecturally defined are:

XSAVE State-components
Index Description Enabled with
0 x87 state XCR0[a]
1 SSE state: XMM0-XMM15 and MXCSR XCR0
2 AVX state: top halves of YMM0 to YMM15
3 MPX state: BND0-BND3 bounds registers
4 MPX state: BNDCFGU and BNDSTATUS registers
5 AVX-512 state: opmask registers k0-k7
6 AVX-512 "ZMM_Hi256" state: top halves of ZMM0 to ZMM15
7 AVX-512 "Hi16_ZMM" state: ZMM16-ZMM31
8 Processor Trace state IA32_XSS
9 PKRU (User Protection Keys) register XCR0
10 PASID (Process Address Space ID) state IA32_XSS
11 CET_U state (Control-flow Enforcement Technology: user-mode functionality MSRs)
12 CET_S state (CET: shadow stack pointers for rings 0,1,2)
13 HDC (Hardware Duty Cycling) state
14 UINTR (User-Mode Interrupts) state
15 LBR (Last Branch Record) state
16 HWP (Hardware P-state control) state
17 AMX tile configuration state: TILECFG XCR0
18 AMX tile data registers: tmm0-tmm7
19 APX extended general-purpose registers: r16-r31[95]

20 to 61
62 Lightweight Profiling (LWP) (AMD only) XCR0
63 (reserved)[b]
  1. ^ Bit 0 of XCR0 is hardwired to 1, so that the XSAVE instructions will always support save/restore of x87 state.
  2. ^ For the XCR0 and IA32_XSS registers, bit 63 is reserved specifically for bit vector expansion - this precludes the existence of a state-component 63.

EAX=12h: SGX capabilities[edit]

This leaf provides information about the supported capabilities of the Intel Software Guard Extensions (SGX) feature. The leaf provides multiple sub-leaves, selected with ECX.

Sub-leaf 0 provides information about supported SGX leaf functions in EAX and maximum supported SGX enclave sizes in EDX; ECX is reserved. EBX provides a bitmap of bits that can be set in the MISCSELECT field in the SECS (SGX Enclave Control Structure) - this field is used to control information written to the MISC region of the SSA (SGX Save State Area) when an AEX (SGX Asynchronous Enclave Exit) occurs.

CPUID EAX=12h,ECX=0: SGX leaf functions, MISCSELECT and maximum-sizes
Short Feature Short Feature Short Feature
0 sgx1 SGX1 leaf functions EXINFO MISCSELECT: report information about page fault and general protection exception that occurred inside enclave MaxEnclave­Size_Not64 Log2 of maximum enclave size supported in non-64-bit mode 0
1 sgx2 SGX2 leaf functions CPINFO MISCSELECT: report information about control protection exception that occurred inside enclave 1
2 (reserved) (reserved) 2
3 (reserved) (reserved) 3
4 (reserved) (reserved) 4
6 ENCLS leaves: ETRACKC, ERDINFO, ELDBC, ELDUC (reserved) 6
7 ENCLU leaf: EVERIFYREPORT2 (reserved) 7
8 (reserved) (reserved) MaxEnclave­Size_64 Log2 of maximum enclave size supported in 64-bit mode 8
9 (reserved) (reserved) 9
10 ENCLS leaf: EUPDATESVN (reserved) 10
11 ENCLU leaf: EDECSSA (reserved) 11
12 (reserved) (reserved) 12
13 (reserved) (reserved) 13
14 (reserved) (reserved) 14
15 (reserved) (reserved) 15

(reserved) (reserved) (reserved)

Sub-leaf 1 provides a bitmap of which bits can be set in the 128-bit ATTRIBUTES field of SECS in EDX:ECX:EBX:EAX (this applies to the SECS copy used as input to the ENCLS[ECREATE] leaf function). The top 64 bits (given in EDX:ECX) are a bitmap of which bits can be set in the XFRM (X-feature request mask) - this mask is a bitmask of which CPU state-components (see leaf 0Dh) will be saved to the SSA in case of an AEX; this has the same layout as the XCR0 control register. The other bits are given in EAX and EBX, as follows:

CPUID EAX=12h,ECX=1: SGX settable bits in SECS.ATTRIBUTES
Short Feature Short Feature
0 (INIT) (must be 0)[a] (reserved) 0
1 DEBUG Permit debugger to read and write enclave data using EDBGRD and EDBGWR 1
2 MODE64BIT 64-bit-mode enclave 2
3 (reserved) 3
4 PROVISIONKEY Provisioning key available from EGETKEY 4
5 EINITTOKEN_KEY EINIT token key available from EGETKEY 5
6 CET CET (Control-Flow Enforcement Technology) attributes enable 6
7 KSS Key Separation and Sharing 7
8 (reserved) 8
9 (reserved) 9
10 AEXNOTIFY Threads inside enclave may receive AEX notifications[98] 10

  1. ^ For the copy of the SECS that exists inside an exclave, bit 0 (INIT) of SECS.ATTRIBUTES is used to indicate that the enclave has been initialized with ENCLS[EINIT]. This bit must be 0 in the SECS copy that is given as input to ENCLS[CREATE].

Sub-leaves 2 and up are used to provide information about which physical memory regions are available for use as EPC (Enclave Page Cache) sections under SGX.

CPUID EAX=12h,ECX≥2: SGX Enclave Page Cache section information
3:0 Sub-leaf type:
  • 0000: Invalid
  • 0001: EPC section
  • other: reserved
Bits 51:32 of physical base address of EPC section EPC Section properties:
  • 0000: Invalid
  • 0001: Has confidentiality, integrity and replay protection
  • 0010: Has confidentiality protection only
  • 0011: Has confidentiality and integrity protection
  • other: reserved
Bits 51:32 of size of EPC section 3:0

(reserved) (reserved)

Bits 31:12 of physical base address of EPC section Bits 31:12 of size of EPC section

(reserved) (reserved)

EAX=14h, ECX=0: Processor Trace[edit]

This sub-leaf provides feature information for Intel Processor Trace (also known as Real Time Instruction Trace).

The value returned in EAX is the index of the highest sub-leaf supported for CPUID with EAX=14h. EBX and ECX provide feature flags, EDX is reserved.

CPUID EAX=14h,ECX=0: Processor Trace feature bits in EBX and ECX
Short Feature Short Feature
0 CR3 filtering supported topaout ToPA (Table of Physical Addresses) output mechanism for trace packets supported 0
1 Configurable PSB (Packet Stream Boundary) packet rate and Cycle-Accurate Mode (CYC packets) supported mentry ToPA tables can contain hold multiple output entries 1
2 IP filtering, TraceStop filtering and preservation of PT MSRs across warm reset supported snglrngout Single-Range Output scheme supported 2
3 MTC (Mini Time Counter) timing packets supported, and suppression of COFI (Change of Flow Instructions) packets supported. Output to Trace Transport subsystem supported 3
4 ptwrite PTWRITE instruction supported (reserved) 4
5 Power Event Trace supported (reserved) 5
6 Preservation of PSB and PMI (performance monitoring interrupt) supported (reserved) 6
7 Event Trace packet generation supported (reserved) 7
8 TNT (Branch Taken-Not-Taken) packet generation disable supported. (reserved) 8
9 PTTT (Processor Trace Trigger Tracing) supported (reserved) 9

(reserved) (reserved)
31 (reserved) IP (Instruction Pointer) format for trace packets that contain IP payloads:
  • 0=RIP (effective-address IP)
  • 1=LIP (linear-address IP, with CS base address added)

EAX=15h and EAX=16h: CPU, TSC, Bus and Core Crystal Clock frequencies[edit]

These two leaves provide information about various frequencies in the CPU in EAX, EBX and ECX (EDX is reserved in both leaves).

CPUID EAX=15h: TSC and Core Crystal frequency information
Ratio of TSC frequency to Core Crystal Clock frequency, denominator Ratio of TSC frequency to Core Crystal Clock frequency, numerator[a] Core Crystal Clock frequency, in units of Hz[a]
CPUID EAX=16h: Processor and Bus specification frequencies[b]
15:0 Processor Base Frequency (in MHz)[a] Processor Maximum Frequency (in MHz)[a] Bus/Reference frequency (in MHz)[a] 15:0
31:16 (reserved) (reserved) (reserved) 31:16
  1. ^ a b c d e Field not enumerated if zero.
  2. ^ The frequency values reported by leaf 16h are the processor's specification frequencies - they are constant for the given processor and do not necessarily reflect the actual CPU clock speed at the time CPUID is called.

If the returned values in EBX and ECX of leaf 15h are both nonzero, then the TSC (Time Stamp Counter) frequency in Hz is given by TSCFreq = ECX*(EBX/EAX).

On some processors (e.g. Intel Skylake), CPUID_15h_ECX is zero but CPUID_16h_EAX is present and not zero. On all known processors where this is the case,[99] the TSC frequency is equal to the Processor Base Frequency, and the Core Crystal Clock Frequency in Hz can be computed as CoreCrystalFreq = (CPUID_16h_EAX * 10000000) * (CPUID_15h_EAX/CPUID_15h_EBX).

On processors that enumerate the TSC/Core Crystal Clock ratio in CPUID leaf 15h, the APIC timer frequency will be the Core Crystal Clock frequency divided by the divisor specified by the APIC's Divide Configuration Register.[100]

EAX=17h: SoC Vendor Attribute Enumeration[edit]

This leaf is present in systems where an x86 CPU IP core is implemented in an SoC (System on chip) from another vendor - whereas the other leaves of CPUID provide information about the x86 CPU core, this leaf provides information about the SoC. This leaf takes a sub-leaf index in ECX.

Sub-leaf 0 returns a maximum sub-leaf index in EAX (at least 3), and SoC identification information in EBX/ECX/EDX:

CPUID EAX=17h,ECX=0: SoC identification information
15:0 SoC Vendor ID SoC Project ID SoC Stepping ID within an SoC project 15:0
16 SoC Vendor ID scheme
  • 0 : Vendor IDs assigned by Intel[a]
  • 1 : Industry standard enumeration scheme[b]
31:17 (reserved) 31:17
  1. ^ As of May 2024, the following Vendor IDs are known to have been assigned by Intel:
    ID Vendor
    1 Spreadtrum[101]
  2. ^ As of May 2024, Intel documentation does not specify which "Industry Standard" enumeration scheme to use for the Vendor ID in EBX[15:0] if EBX[16] is set.

Sub-leaves 1 to 3 return a 48-byte SoC vendor brand string in UTF-8 format. Sub-leaf 1 returns the first 16 bytes in EAX,EBX,ECX,EDX (in that order); sub-leaf 2 returns the next 16 bytes and sub-leaf 3 returns the last 16 bytes. The string is allowed but not required to be null-terminated.

EAX=19h: Intel Key Locker features[edit]

This leaf provides feature information for Intel Key Locker in EAX, EBX and ECX. EDX is reserved.

CPUID EAX=19h: Key Locker feature bits in EAX, EBX and ECX
Short Feature Short Feature Short Feature
0 Key Locker restriction of CPL0-only supported aes_kle AES "Key Locker" Instructions enabled No-backup parameter to LOADIWKEY supported 0
1 Key Locker restriction of no-encrypt supported (reserved) KeySource encoding of 1 (randomization of internal wrapping key) supported 1
2 Key Locker restriction of no-decrypt supported aes_wide_kl AES "Wide Key Locker" Instructions (reserved) 2
3 (Process Restriction)[a] (reserved) (reserved) 3
4 (reserved) kl_msrs "Key Locker" MSRs (reserved) 4

(reserved) (reserved) (reserved)
  1. ^ As of April 2024, the "Process Restriction" bit is listed only in Intel TDX documentation[86] and is not set in any known processor.

EAX=21h: Reserved for TDX enumeration[edit]

When Intel TDX (Trust Domain Extensions) is active, attempts to execute the CPUID instruction by a TD (Trust Domain) guest will be intercepted by the TDX module. This module will, when CPUID is invoked with EAX=21h and ECX=0 (leaf 21h, sub-leaf 0), return the index of the highest supported sub-leaf for leaf 21h in EAX and a TDX module vendor ID string as a 12-byte ASCII string in EBX,EDX,ECX (in that order). Intel's own module implementation returns the vendor ID string "IntelTDX    " (with four trailing spaces)[102] - for this module, additional feature information is not available through CPUID and must instead be obtained through the TDX-specific TDCALL instruction.

This leaf is reserved in hardware and will (on processors whose highest basic leaf is 21h or higher) return 0 in EAX/EBX/ECX/EDX when run directly on the CPU.

EAX=24h, ECX=0: AVX10 Features[edit]

This returns a maximum supported sub-leaf in EAX and AVX10 feature information in EBX.[94] (ECX and EDX are reserved.)

CPUID EAX=24h, ECX=0: AVX10 feature bits in EBX
Short Feature
7:0 AVX10 Converged Vector ISA version (≥1)
15:8 (reserved)
16 avx10-128 128-bit vector support is present
17 avx10-256 256-bit vector support is present
18 avx10-512 512-bit vector support is present
31:19 (reserved)

EAX=24h, ECX=1: Discrete AVX10 Features[edit]

Subleaf 1 is reserved for AVX10 features not bound to a version. None are currently defined.

EAX=40000000h-4FFFFFFFh: Reserved for Hypervisor use[edit]

When the CPUID instruction is executed under Intel VT-x or AMD-v virtualization, it will be intercepted by the hypervisor, enabling the hypervisor to return CPUID feature flags that differ from those of the underlying hardware. CPUID leaves 40000000h to 4FFFFFFFh are not implemented in hardware, and are reserved for use by hypervisors to provide hypervisor-specific identification and feature information through this interception mechanism.

For leaf 40000000h, the hypervisor is expected to return the index of the highest supported hypervisor CPUID leaf in EAX, and a 12-character hypervisor ID string in EBX,ECX,EDX (in that order). For leaf 40000001h, the hypervisor may return an interface identification signature in EAX - e.g. hypervisors that wish to advertise that they are Hyper-V compatible may return 0x31237648“Hv#1” in EAX.[103][104] The formats of leaves 40000001h and up to the highest supported leaf are otherwise hypervisor-specific. Hypervisors that implement these leaves will normally also set bit 31 of ECX for CPUID leaf 1 to indicate their presence.

Hypervisors that expose more than one hypervisor interface may provide additional sets of CPUID leaves for the additional interfaces, at a spacing of 100h leaves per interface. For example, when QEMU is configured to provide both Hyper-V and KVM interfaces, it will provide Hyper-V information starting from CPUID leaf 40000000h and KVM information starting from leaf 40000100h.[105][106]

Some hypervisors that are known to return a hypervisor ID string in leaf 40000000h include:

CPUID EAX=40000x00h: 12-character Hypervisor ID string in EBX,ECX,EDX
Hypervisor ID String (ASCII) Notes
Microsoft Hyper-V,
Windows Virtual PC
"Microsoft Hv"[103]
Linux KVM "KVMKVMKVM\0\0\0"[107] \0 denotes an ASCII NUL character.
"Linux KVM Hv"[108] Hyper-V emulation[109]
bhyve "BHyVE BHyVE ",
"bhyve bhyve "
ID string changed from mixed-case to lower-case in 2013.[110]

Lower-case string also used in bhyve-derived hypervisors such as xhyve and HyperKit.[111]

Xen "XenVMMXenVMM"[112] Only when using HVM (hardware virtual machine) mode.
QEMU "TCGTCGTCGTCG"[113] Only when the TCG (Tiny Code Generator) is enabled.
Parallels " lrpepyh  vr" (it possibly should be "prl hyperv", but it is encoded as " lrpepyh vr" due to an endianness mismatch)[citation needed]
VMware "VMwareVMware"[114]
VirtualBox "VBoxVBoxVBox"[116] Only when configured to use the "hyperv" paravirtualization provider.
QNX Hypervisor "QXNQSBMV" The QNX hypervisor detection method provided in the official QNX documentation[117] checks only the first 8 characters of the string, as provided in EBX and ECX (including an endianness swap) - EDX is ignored and may take any value.
NetBSD NVMM "___ NVMM ___"[118]
OpenBSD VMM "OpenBSDVMM58"[119]
Intel HAXM "HAXMHAXMHAXM"[120] Project discontinued.
Intel KGT (Trusty) "EVMMEVMMEVMM"[121] On "trusty" branch of KGT only, which is used for the Intel x86 Architecture Distribution of Trusty OS (archive)

(KGT also returns a signature in CPUID leaf 3: ECX=0x4D4D5645 "EVMM" and EDX=0x43544E49 "INTC")

Unisys s-Par "UnisysSpar64"[122]
Lockheed Martin LMHS "SRESRESRESRE"[123]

EAX=80000000h: Get Highest Extended Function Implemented[edit]

The highest calling parameter is returned in EAX.

EBX/ECX/EDX return the manufacturer ID string (same as EAX=0) on AMD but not Intel CPUs.

EAX=80000001h: Extended Processor Info and Feature Bits[edit]

This returns extended feature flags in EDX and ECX.

Many of the bits in EDX (bits 0 through 9, 12 through 17, 23, and 24) are duplicates of EDX from the EAX=1 leaf - these bits are highlighted in light yellow. (These duplicated bits are present on AMD but not Intel CPUs.)

AMD feature flags are as follows:[124][125]

CPUID EAX=80000001h: Feature bits in EDX and ECX
Short Feature Short Feature
0 fpu Onboard x87 FPU lahf_lm LAHF/SAHF in long mode 0
1 vme Virtual mode extensions (VIF) cmp_legacy Hyperthreading not valid 1
2 de Debugging extensions (CR4 bit 3) svm Secure Virtual Machine 2
3 pse Page Size Extension extapic Extended APIC space 3
4 tsc Time Stamp Counter cr8_legacy CR8 in 32-bit mode 4
5 msr Model-specific registers abm/lzcnt Advanced bit manipulation (LZCNT and POPCNT) 5
6 pae Physical Address Extension sse4a SSE4a 6
7 mce Machine Check Exception misalignsse Misaligned SSE mode 7
8 cx8 CMPXCHG8B (compare-and-swap) instruction 3dnowprefetch PREFETCH and PREFETCHW instructions 8
9 apic Onboard Advanced Programmable Interrupt Controller osvw OS Visible Workaround 9
10 (syscall)[a] (SYSCALL/SYSRET, K6 only) ibs Instruction Based Sampling 10
11 syscall[b] SYSCALL and SYSRET instructions xop XOP instruction set 11
12 mtrr Memory Type Range Registers skinit SKINIT/STGI instructions 12
13 pge Page Global Enable bit in CR4 wdt Watchdog timer 13
14 mca Machine check architecture (reserved) 14
15 cmov Conditional move and FCMOV instructions lwp Light Weight Profiling[129] 15
16 pat[c] Page Attribute Table fma4 4-operand fused multiply-add instructions 16
17 pse36 36-bit page size extension tce Translation Cache Extension 17
18 (reserved) (reserved) 18
19 ecc "Athlon MP" / "Sempron" CPU brand identification[d] nodeid_msr NodeID MSR (C001_100C)[134] 19
20 nx NX bit (reserved) 20
21 (reserved) tbm Trailing Bit Manipulation 21
22 mmxext Extended MMX topoext Topology Extensions 22
23 mmx MMX instructions perfctr_core Core performance counter extensions 23
24 fxsr[c] FXSAVE, FXRSTOR instructions, CR4 bit 9 perfctr_nb Northbridge performance counter extensions 24
25 fxsr_opt FXSAVE/FXRSTOR optimizations (StreamPerfMon) (Streaming performance monitor architecture)[e] 25
26 pdpe1gb Gigabyte pages dbx Data breakpoint extensions 26
27 rdtscp RDTSCP instruction perftsc Performance timestamp counter (PTSC) 27
28 (reserved) pcx_l2i L2I perf counter extensions 28
29 lm Long mode monitorx MONITORX and MWAITX instructions 29
30 3dnowext Extended 3DNow! addr_mask_ext Address mask extension to 32 bits for instruction breakpoints 30
31 3dnow 3DNow! (reserved) 31
  1. ^ The use of EDX bit 10 to indicate support for SYSCALL/SYSRET is only valid on AuthenticAMD Family 5 Model 7 CPUs (AMD K6, 250nm "Little Foot") - for all other processors, EDX bit 11 should be used instead.

    These instructions were first introduced on Model 7[126] - the CPUID bit to indicate their support was moved[127] to EDX bit 11 from Model 8 (AMD K6-2) onwards.

  2. ^ On Intel CPUs, the CPUID bit for SYSCALL/SYSRET is only set if the CPUID instruction is executed in 64-bit mode.[128]
  3. ^ a b On some processors - Cyrix MediaGXm,[130] several Geodes (NatSemi Geode GXm, GXLV, GX1; AMD Geode GX1[131]) and Transmeta Crusoe[132] - EDX bits 16 and 24 have a different meaning:
    • Bit 16: Floating-point Conditional Move (FCMOV) supported
    • Bit 24: 6x86MX Extended MMX instructions supported
  4. ^ EDX bit 19 is used for CPU brand identification on AuthenticAMD Family 6 processors only - the bit is, combined with processor signature and FSB speed, used to identify processors as either multiprocessor-capable or carrying the Sempron brand name.[133]
  5. ^ ECX bit 25 is listed as StreamPerfMon in revision 3.20 of AMD APM[135] only - it is listed as reserved in later revisions. The bit is set on Excavator and Steamroller CPUs only.

EAX=80000002h,80000003h,80000004h: Processor Brand String[edit]

These return the processor brand string in EAX, EBX, ECX and EDX. CPUID must be issued with each parameter in sequence to get the entire 48-byte ASCII processor brand string.[136] It is necessary to check whether the feature is present in the CPU by issuing CPUID with EAX = 80000000h first and checking if the returned value is not less than 80000004h.

The string is specified in Intel/AMD documentation to be null-terminated, however this is not always the case (e.g. DM&P Vortex86DX3 and AMD Ryzen 7 6800HS are known to return non-null-terminated brand strings in leaves 80000002h-80000004h[137][138]), and software should not rely on it.

#include <stdio.h> #include <string.h> #include <cpuid.h>  int main() {     unsigned int regs[12];     char str[sizeof(regs)+1];      __cpuid(0x80000000, regs[0], regs[1], regs[2], regs[3]);      if (regs[0] < 0x80000004)         return 1;      __cpuid(0x80000002, regs[0], regs[1], regs[2], regs[3]);     __cpuid(0x80000003, regs[4], regs[5], regs[6], regs[7]);     __cpuid(0x80000004, regs[8], regs[9], regs[10], regs[11]);      memcpy(str, regs, sizeof(regs));     str[sizeof(regs)] = '\0';     printf("%s\n", str);      return 0; } 

On AMD processors, from 180nm Athlon onwards (AuthenticAMD Family 6 Model 2 and later), it is possible to modify the processor brand string returned by CPUID leaves 80000002h-80000004h by using the WRMSR instruction to write a 48-byte replacement string to MSRs C0010030h-C0010035h.[133][139] This can also be done on AMD Geode GX/LX, albeit using MSRs 300Ah-300Fh.[140]

In some cases, determining the CPU vendor requires examining not just the Vendor ID in CPUID leaf 0 and the CPU signature in leaf 1, but also the Processor Brand String in leaves 80000002h-80000004h. Known cases include:

  • Montage Jintide CPUs can be distinguished from the Intel Xeon CPU models they're based on by the presence of the substring Montage in the brand string of the Montage CPUs (e.g. Montage Jintide C2460[141] and Intel Xeon Platinum 8160[142] - both of which identify themselves as GenuineIntel Family 6 Model 55h Stepping 4 - can be distinguished in this manner.)
  • CentaurHauls Family 6 CPUs may be either VIA or Zhaoxin CPUs - these can be distinguished by the presence of the substring ZHAOXIN in the brand string of the Zhaoxin CPUs (e.g. Zhaoxin KaiXian ZX-C+ C4580[143] and VIA Eden X4 C4250[144] - both of which identify themselves as CentaurHauls Family 6 Model 0Fh Stepping 0Eh - can be distinguished in this manner.)

EAX=80000005h: L1 Cache and TLB Identifiers[edit]

This provides information about the processor's level-1 cache and TLB characteristics in EAX, EBX, ECX and EDX as follows:[a]

  • EAX: information about L1 hugepage TLBs (TLBs that hold entries corresponding to 2M/4M pages)[b]
  • EBX: information about L1 small-page TLBs (TLBs that hold entries corresponding to 4K pages)
  • ECX: information about L1 data cache
  • EDX: information about L1 instruction cache
CPUID EAX=80000002h: L1 Cache/TLB information in EAX,EBX,ECX,EDX
7:0 Number of instruction TLB entries[c] Cache line size in bytes 7:0
15:8 instruction TLB associativity[d] Number of cache lines per tag 15:8
23:16 Number of data TLB entries[c] Cache associativity[d] 23:16
31:24 Data TLB associativity[d] Cache size in kilobytes 31:24
  1. ^ On some older Cyrix and Geode CPUs (specifically, CyrixInstead/Geode by NSC Family 5 Model 4 CPUs only), leaf 80000005h exists but has a completely different format, similar to that of leaf 2.[145]
  2. ^ On processors that can only handle small-pages in their TLBs, this leaf will return 0 in EAX. (On such processors, which include e.g. AMD K6 and Transmeta Crusoe, hugepage entries in the page-tables are broken up into 4K pages as needed upon entry into the TLB.)
    On some processors, e.g. VIA Cyrix III "Samuel",[146] this leaf returns 0x80000005 in EAX. This has the same meaning as EAX=0, i.e. no hugepage TLBs.
  3. ^ a b On Transmeta CPUs, the value FFh is used to indicate a 256-entry TLB.
  4. ^ a b c For the associativity fields of leaf 80000005h, the following values are used:
    Value Meaning
    0 (reserved)
    1 Direct-mapped
    2 to FEh N-way set-associative (field encodes N)
    FFh Fully-associative

EAX=80000006h: Extended L2 Cache Features[edit]

Returns details of the L2 cache in ECX, including the line size in bytes (Bits 07 - 00), type of associativity (encoded by a 4 bits field; Bits 15 - 12) and the cache size in KB (Bits 31 - 16).

#include <stdio.h> #include <cpuid.h>  int main() {     unsigned int eax, ebx, ecx, edx;     unsigned int lsize, assoc, cache;      __cpuid(0x80000006, eax, ebx, ecx, edx);          lsize = ecx & 0xff;     assoc = (ecx >> 12) & 0x07;     cache = (ecx >> 16) & 0xffff;      printf("Line size: %d B, Assoc. type: %d, Cache size: %d KB.\n", lsize, assoc, cache);      return 0; } 

EAX=80000007h: Processor Power Management Information and RAS Capabilities[edit]

This function provides information about power management, power reporting and RAS (Reliability, availability and serviceability) capabilities of the CPU.

CPUID EAX=80000007h: RAS features in EBX and power management features in EDX
Short Feature Short Feature
0 MCAOverflowRecov MCA (Machine Check Architecture) overflow recovery support TS Temperature Sensor 0
1 SUCCOR Software uncorrectable error containment and recovery capability FID Frequency ID Control 1
2 HWA Hardware assert support (MSRs C001_10C0 to C001_10DF VID Voltage ID Control 2
3 ScalableMca Scalable MCA supported TTP THERMTRIP 3
4 (reserved) TM Hardware thermal control (HTC) supported 4
5 (reserved) STC Software thermal control (STC) supported[147] 5
6 (reserved) 100MHzSteps 100 MHz multiplier control 6
7 (reserved) HwPstate Hardware P-state control (MSRs C001_0061 to C001_0063) 7
8 (reserved) TscInvariant Invariant TSC - TSC (Time Stamp Counter) rate is guaranteed to be invariant across all P-states, C-states and sop grant transitions. 8
9 (reserved) CPB Core Performance Boost 9
10 (reserved) EffFreqRO Read-only effective frequency interface (MSRs C000_00E7 and C000_00E8) 10
11 (reserved) ProcFeedback­Interface Processor Feedback Interface supported 11
12 (reserved) ProcPower­Reporting Processor power reporting interface supported 12
13 (reserved) Connected­Standby Connected Standby[148] 13
14 (reserved) RAPL Running Average Power Limit[148] 14
15 (reserved) FastCPPC Fast CPPC (Collaborative Processor Performance Control) supported[148] 15

(reserved) (reserved)
CPUID EAX=80000007h: Processor Feedback info in EAX and power monitoring interface info in ECX
Bits EAX ECX Bits
Short Feature Short Feature
7:0 NumberOfMonitors Number of Processor Feedback MSR pairs available, starting from MSR C001_0080 onwards[149] CpuPwrSample­TimeRatio Ratio of compute unit power accumulator sample period to TSC counter period. 7:0
15:8 Version Processor Feedback Capabilities version 15:8
31:16 MaxWrapTime Maximum time between reads (in milliseconds) that software should use to avoid two wraps. 31:16

EAX=80000008h: Virtual and Physical address Sizes[edit]

CPUID EAX=80000008h: Feature bits in EBX
Short Feature
0 clzero CLZERO instruction
1 retired_instr Retired instruction count MSR (C000_00E9h) supported
2 xrstor_fp_err XRSTOR restores FP errors
3 invlpgb INVLPGB and TLBSYNC instructions
4 rdpru RDPRU instruction
5 (reserved)
6 mbe Memory Bandwidth Enforcement
7 (reserved)
8 mcommit MCOMMIT instruction
9 wbnoinvd WBNOINVD instruction
10 (reserved)
11 (reserved)
12 IBPB Indirect Branch Prediction Barrier (performed by writing 1 to bit 0 of PRED_CMD (MSR 049h))
13 wbinvd_int WBINVD and WBNOINVD are interruptible
14 IBRS Indirect Branch Restricted Speculation
15 STIBP Single Thread Indirect Branch Prediction mode
16 IbrsAlwaysOn IBRS mode has enhanced performance and should be left always on
17 StibpAlwaysOn STIBP mode has enhanced performance and should be left always on
18 ibrs_preferred IBRS preferred over software
19 ibrs_same_mode_protection IBRS provides Same Mode Protection
20 no_efer_lmsle EFER.LMSLE is unsupported[a]
21 invlpgb_nested INVLPGB support for nested pages
22 (reserved)
23 ppin Protected Processor Inventory Number -

PPIN_CTL (C001_02F0) and PPIN (C001_02F1) MSRs are present[148]

24 ssbd Speculative Store Bypass Disable
25 ssbd_legacy Speculative Store Bypass Disable Legacy
26 ssbd_no Speculative Store Bypass Disable Not Required
27 cppc Collaborative Processor Performance Control
28 psfd Predictive Store Forward Disable
29 btc_no Branch Type Confusion: Processor not affected
30 IBPB_RET IBPB (see bit 12) also clears return address predictor
31 branch_sampling Branch Sampling Support[151]
CPUID EAX=80000008h: Size and range fields in EAX, ECX, EDX
7:0 Number of Physical Address Bits Number of Physical Threads in processor (minus 1) Maximum page count for INVLPGB instruction 7:0
11:8 Number of Linear Address Bits (reserved) 11:8
15:12 APIC ID Size 15:12
17:16 Guest Physical Address Size[b] Performance Timestamp Counter size Maximum ECX value recognized by RDPRU instruction 17:16
23:18 (reserved) 23:18
31:24 (reserved) 31:24
  1. ^ The LMSLE (Long Mode Segment Limit Enable) feature does not have its own CPUID flag and is detected by checking CPU family and model. It was introduced in AuthenticAMD Family 0Fh Model 14h[150] (90nm Athlon64/Opteron) CPUs and is present in all later AMD CPUs - except the ones with the 'no_efer_lmsle' flag set.
  2. ^ A value of 0 indicates that the "Guest Physical Address Size" is the same as the "Number Of Physical Address Bits", specified in EAX[7:0].

EAX=8000000Ah: Secure Virtual Machine features[edit]

This leaf returns information about AMD SVM (Secure Virtual Machine) features in EAX, EBX and EDX.

CPUID EAX=8000000Ah: SVM information in EAX, EBX and ECX
7:0 SVM Revision Number Number of available ASIDs
(address space identifiers)
(reserved) 7:0
8 (hypervisor)[a] 8
31:9 (reserved) 31:9
CPUID EAX=8000000Ah: SVM feature flags in EDX
Short Feature
0 NP Rapid Virtualization Indexing (Nested Paging)
1 LbrVirt LBR (Last Branch Records) virtualization
3 NRIPS nRIP (next sequential instruction pointer) save on #VMEXIT supported
4 TscRateMsr MSR-based TSC rate control (MSR C000_0104h)
5 VmcbClean VMCB (Virtual Machine Control Block) clean bits supported
6 FlushByAsid TLB flush events (e.g. CR3 writes, CR4.PGE toggles) only flush the TLB entries of the current ASID (address space ID)
7 DecodeAssist Decode assists supported
8 PmcVirt PMC (Performance Monitoring Counters) virtualization
9 (SseIsa10Compat)[b] (reserved)
10 PauseFilter PAUSE intercept filter supported
11 (reserved)
12 PauseFilter­Threshold PAUSE filter cycle count threshold supported
13 AVIC AMD Advanced Virtualized Interrupt Controller supported
14 (reserved)
15 VMSAVEvirt VMSAVE and VMLOAD virtualization
16 VGIF Global Interrupt Flag (GIF) virtualization
17 GMET Guest Mode Execution Trap
18 x2AVIC x2APIC mode supported for AVIC
19 SSSCheck SVM Supervisor shadow stack restrictions
20 SpecCtrl SPEC_CTRL (MSR 2E0h) virtualization
21 ROGPT Read-Only Guest Page Table supported
22 (reserved)
23 HOST_MCE_­OVERRIDE Guest mode Machine-check exceptions when host CR4.MCE=1 and guest CR4.MCE=0 cause intercepts instead of shutdowns
24 TlbiCtl INVLPGB/TLBSYNC hypervisor enable in VMCB and TLBSYNC intercept support
25 VNMI NMI (Non-Maskable interrupt) virtualization
26 IbsVirt IBS (Instruction-Based Sampling) virtualization
27 ExtLvtOffset­FaultChg Read/Write fault behavior for extended LVT offsets (APIC addresses 0x500-0x530) changed to Read Allowed, Write #VMEXIT[158]
28 VmcbAddr­ChkChg VMCB address check change[158]
29 BusLock­Threshold Bus Lock Threshold
30 IdleHlt­Intercept Idle HLT (HLT instruction executed while no virtual interrupt is pending) intercept
31 (reserved)
  1. ^ Early revisions of AMD's "Pacifica" documentation listed EAX bit 8 as an always-zero bit reserved for hypervisor use.[152]

    Later AMD documentation, such as #25481 "CPUID specification" rev 2.18[153] and later, only lists the bit as reserved.

    In rev 2.30[154] and later, a different bit is listed as reserved for hypervisor use: CPUID.(EAX=1):ECX[bit 31].

  2. ^ EDX bit 9 is briefly listed in some older revisions of AMD's document #25481 "CPUID Specification", and is set only in some AMD Bobcat CPUs.[155]

    Rev 2.28 of #25481 lists the bit as "Ssse3Sse5Dis"[156] - in rev 2.34, it is listed as having been removed from the spec at rev 2.32 under the name "SseIsa10Compat".[157]

EAX=8000001Fh: Encrypted Memory Capabilities[edit]

CPUID EAX=8000001Fh: Encrypted Memory feature bits in EAX
Short Feature
0 SME Secure Memory Encryption
1 SEV Secure Encrypted Virtualization
2 PageFlushMSR Page flush MSR (C001_011Eh) supported
3 SEV-ES SEV Encrypted State
4 SEV-SNP SEV Secure Nested Paging
5 VMPL VM Privilege Levels
6 RMPQUERY RMPQUERY instruction supported
7 VmplSSS VMPL Supervisor shadow stack supported
8 SecureTSC Secure TSC supported
9 TscAux­Virtualization Virtualization of TSC_AUX MSR (C000_0103) supported
10 HwEnfCacheCoh Hardware cache coherency across encryption domains enforced
11 64BitHost SEV Guest execution only allowed from 64-bit host
12 Restricted­Injection SEV-ES guests can refuse all event-injections except #HV (Hypervisor Injection Exception)
13 Alternate­Injection SEV-ES guests can use an encrypted VMCB field for event-injection
14 DebugVirt Full debug state virtualization supported for SEV-ES and SEV-SNP guests
15 PreventHostIBS Prevent host IBS for a SEV-ES guest
16 VTE Virtual Transparent Encryption for SEV
17 Vmgexit­Parameter VMGEXIT parameter is supported (using the RAX register)
18 VirtualTomMsr Virtual TOM (top-of-memory) MSR (C001_0135) supported
19 IbsVirtGuestCtl IBS virtualization is supported for SEV-ES and SEV-SNP guests
20 PmcVirtGuestCtl PMC virtualization is supported for SEV-ES and SEV-SNP guests
21 RMPREAD RMPREAD instruction supported
22 (reserved)
23 (reserved)
24 VmsaRegProt VMSA (VM Save Area) register protection supported
25 SmtProtection SMT Protection supported
26 SecureAvic Secure AVIC supported
27 AllowedSEV­features ALLOWED_SEV_FEATURES_MASK field in VMCB (offset 138h) supported
28 SVSMComm­PageMSR SVSM (Secure VM Service Module[159]) communication page MSR (C001_F000h) supported
29 NestedVirt­SnpMsr VIRT_RMPUPDATE (C001_F001h) and VIRT_PSMASH (C001_F002h) MSRs supported
30 HvInUse­WrAllowed Writes to Hypervisor-owned paged allowed when marked in-use
31 IbpbOnEntry IBPB on entry to virtual machine supported
CPUID EAX=8000001Fh: Encrypted Memory feature information in EBX, ECX and EDX
5:0 C-bit (encryption enable bit) location in page table entry Maximum ASID value that can be used for a SEV-enabled guest (maximum number of encrypted guests that can be supported simultaneously) Minimum ASID value for a guest that is SEV-enabled but not SEV-ES-enabled 5:0
11:6 Physical address width reduction when memory encryption is enabled 11:6
15:12 Number of VMPLs (VM Privilege Levels) supported 15:12
31:16 (reserved) 31:16

EAX=80000021h: Extended Feature Identification 2[edit]

CPUID EAX=80000021h: Extended feature bits in EAX
Short Feature
0 NoNestedDataBp Processor ignores nested data breakpoints
1 FsGsKernelGsBase­NonSerializing WRMSR to the FS_BASE, GS_BASE and KernelGSBase MSRs is non-serializing[160]
2 LFenceAlways­Serializing LFENCE is always dispatch serializing
3 SmmPgCfgLock SMM paging configuration lock supported
4 (reserved)
5 (reserved)
6 NullSelect­ClearsBase Null segment selector loads also clear the destination segment register base and limit
7 UpperAddress­Ignore Upper Address Ignore is supported
8 AutomaticIBRS Automatic IBRS
9 NoSmmCtlMSR SMM_CTL MSR (C0010116h) is not supported
10 FSRS Fast short REP STOSB supported
11 FSRC Fast short REPE CMPSB supported
12 (reserved)
13 PrefetchCtlMsr PrefetchControl MSR (C0000108h) is supported
14 (reserved)
15 (reserved)
16 (reserved)
17 CpuidUserDis CPUID disable for non-privileged software
18 EPSF Enhanced Predictive Store Forwarding supported[160]
19 (reserved)
20 (reserved)
21 (reserved)
22 (reserved)
23 (reserved)
24 (reserved)
25 (reserved)
26 (reserved)
27 SBPB Selective Branch Predictor Barrier supported[161]
28 IBPB_BRTYPE IBPB flushes all branch type predictions[161]
29 SRSO_NO CPU is not subject to SRSO (Speculative Return Stack Overflow) vulnerability[161]
30 SRSO_USER_­KERNEL_NO CPU is not subject to SRSO vulnerability across user/kernel boundary[161]
31 SRSO_MSR_FIX SRSO can be mitigated by setting bit 4 of BP_CFG (MSR C001_102E)[161]
CPUID EAX=80000021h: Extended feature information in EBX
Short Feature
11:0 MicrocodePatchSize The size of the Microcode patch in 16-byte multiples. If 0, the size of the patch is at most 5568 (15C0h) bytes
31:12 (reserved)

EAX=8FFFFFFFh: AMD Easter Egg[edit]

Several AMD CPU models will, for CPUID with EAX=8FFFFFFFh, return an Easter Egg string in EAX, EBX, ECX and EDX.[162][163] Known Easter Egg strings include:

Processor String
AMD K6 NexGen‍erationAMD
AMD Jaguar[164] HELLO KITTY! ^-^

EAX=C0000000h: Get Highest Centaur Extended Function[edit]

Returns index of highest Centaur leaf in EAX. If the returned value in EAX is less than C0000001h, then Centaur extended leaves are not supported.

Present in CPUs from VIA and Zhaoxin.

On IDT WinChip CPUs (CentaurHauls Family 5), the extended leaves C0000001h-C0000005h do not encode any Centaur-specific functionality but are instead aliases of leaves 80000001h-80000005h.[165]

EAX=C0000001h: Centaur Feature Information[edit]

This leaf returns Centaur feature information (mainly VIA PadLock) in EDX.[166][167] (EAX, EBX and ECX are reserved.)

CPUID EAX=C0000001h: Centaur feature bits in EDX
Short Feature
0 sm2[a] SM2 present
1 sm2_en[a] SM2 enabled
2 rng PadLock RNG present: XSTORE and REP XSTORE instructions
3 rng_en RNG enabled
4 ccs[a] PadLock SM3/SM4 instructions present: CCS_HASH and CCS_ENCRYPT
5 ccs_en[a] SM3/SM4 instructions enabled
6 xcrypt PadLock Advanced Cryptographic Engine (ACE, using AES cipher) present: REP XCRYPT(ECB,CBC,CFB,OFB) instructions
7 xcrypt_en ACE enabled
8 ace2 ACE v2 present: REP XCRYPTCTR instruction, as well as support for digest mode and misaligned data for ACE's REP XCRYPT* instructions.
9 ace2_en ACE v2 enabled
10 phe PadLock Hash Engine (PHE): REP XSHA1 and REP XSHA256 instructions
11 phe_en PHE enabled
12 pmm PadLock Montgomery Multiplier (PMM): REP MONTMUL instruction
13 pmm_en PMM enabled
14 (reserved)
15 zx_fma FMA supported
16 parallax Adaptive P-state control present
17 parallax_en Adaptive P-state control enabled
18 overstress Overstress feature for auto overclock present
19 overstress_en Overstress feature for auto overclock enabled
20 tm3 Thermal Monitor 3 present
21 tm3_en Thermal Monitor 3 enabled
22 rng2 RNG v2: Second generation RNG present
23 rng2_en RNG v2 enabled
24 sem SME feature present
25 phe2 PHE v2: SHA384 and SHA512 present
26 phe2_en PHE v2 enabled
27 xmodx RSA instructions present: XMODEXP and MONTMUL2
28 xmodx_en RSA instructions enabled
29 vex VEX instructions present
30 vex_en VEX instructions enabled
31 stk STK is present
  1. ^ a b c d On VIA Nehemiah and Antaur CPUs (CentaurHauls Family 6 Model 9 only),[168] bits 0,1,4,5 are used differently:

CPUID usage from high-level languages[edit]

Inline assembly[edit]

This information is easy to access from other languages as well. For instance, the C code for gcc below prints the first five values, returned by the cpuid:

#include <stdio.h> #include <cpuid.h>  int main() {     unsigned int i, eax, ebx, ecx, edx;      for (i = 0; i < 5; i++) {         __cpuid(i, eax, ebx, ecx, edx);         printf ("InfoType %x\nEAX: %x\nEBX: %x\nECX: %x\nEDX: %x\n", i, eax, ebx, ecx, edx);     }      return 0; } 

In MSVC and Borland/Embarcadero C compilers (bcc32) flavored inline assembly, the clobbering information is implicit in the instructions:

#include <stdio.h>  int main() {     unsigned int a, b, c, d, i = 0;      __asm {         /* Do the call. */         mov EAX, i;         cpuid;         /* Save results. */         mov a, EAX;         mov b, EBX;         mov c, ECX;         mov d, EDX;     }      printf ("InfoType %x\nEAX: %x\nEBX: %x\nECX: %x\nEDX: %x\n", i, a, b, c, d);     return 0; } 

If either version was written in plain assembly language, the programmer must manually save the results of EAX, EBX, ECX, and EDX elsewhere if they want to keep using the values.

Wrapper functions[edit]

GCC also provides a header called <cpuid.h> on systems that have CPUID. The __cpuid is a macro expanding to inline assembly. Typical usage would be:

#include <stdio.h> #include <cpuid.h>  int main() {     unsigned int eax, ebx, ecx, edx;      __cpuid(0 /* vendor string */, eax, ebx, ecx, edx);     printf("EAX: %x\nEBX: %x\nECX: %x\nEDX: %x\n", eax, ebx, ecx, edx);      return 0; } 

But if one requested an extended feature not present on this CPU, they would not notice and might get random, unexpected results. Safer version is also provided in <cpuid.h>. It checks for extended features and does some more safety checks. The output values are not passed using reference-like macro parameters, but more conventional pointers.

#include <stdio.h> #include <cpuid.h>  int main() {     unsigned int eax, ebx, ecx, edx;      /* 0x81234567 is nonexistent, but assume it exists */     if (!__get_cpuid (0x81234567, &eax, &ebx, &ecx, &edx)) {         printf("Warning: CPUID request 0x81234567 not valid!\n");         return 1;     }      printf("EAX: %x\nEBX: %x\nECX: %x\nEDX: %x\n", eax, ebx, ecx, edx);      return 0; } 

Notice the ampersands in &a, &b, &c, &d and the conditional statement. If the __get_cpuid call receives a correct request, it will return a non-zero value, if it fails, zero.[169]

Microsoft Visual C compiler has builtin function __cpuid() so the cpuid instruction may be embedded without using inline assembly, which is handy since the x86-64 version of MSVC does not allow inline assembly at all. The same program for MSVC would be:

#include <stdio.h> #ifdef __MSVC__     #include <intrin.h> #endif  int main() {     unsigned int regs[4];     int i;      for (i = 0; i < 4; i++) {         __cpuid(regs, i);         printf("The code %d gives %d, %d, %d, %d", regs[0], regs[1], regs[2], regs[3]);     }      return 0; } 

Many interpreted or compiled scripting languages are capable of using CPUID via an FFI library. One such implementation shows usage of the Ruby FFI module to execute assembly language that includes the CPUID opcode.

.NET 5 and later versions provide the System.Runtime.Intrinsics.X86.X86base.CpuId method. For instance, the C# code below prints the processor brand if it supports CPUID instruction:

using System.Runtime.InteropServices; using System.Runtime.Intrinsics.X86; using System.Text;  namespace X86CPUID {     class CPUBrandString {         public static void Main(string[] args) {             if (!X86Base.IsSupported) {                 Console.WriteLine("Your CPU does not support CPUID instruction.");             } else {                 Span<int> raw = stackalloc int[12];              (raw[0], raw[1], raw[2], raw[3]) = X86Base.CpuId(unchecked((int)0x80000002), 0);              (raw[4], raw[5], raw[6], raw[7]) = X86Base.CpuId(unchecked((int)0x80000003), 0);              (raw[8], raw[9], raw[10], raw[11]) = X86Base.CpuId(unchecked((int)0x80000004), 0);                  Span<byte> bytes = MemoryMarshal.AsBytes(raw);                 string brand = Encoding.UTF8.GetString(bytes).Trim();                 Console.WriteLine(brand);             }         }     } } 

CPU-specific information outside x86[edit]

Some of the non-x86 CPU architectures also provide certain forms of structured information about the processor's abilities, commonly as a set of special registers:

  • ARM architectures have a CPUID coprocessor register which requires exception level EL1 or above to access.[170]
  • The IBM System z mainframe processors have a Store CPU ID (STIDP) instruction since the 1983 IBM 4381[171] for querying the processor ID.[172]
  • The IBM System z mainframe processors also have a Store Facilities List Extended (STFLE) instruction which lists the installed hardware features.[172]
  • The MIPS32/64 architecture defines a mandatory Processor Identification (PrId) and a series of daisy-chained Configuration Registers.[173]
  • The PowerPC processor has the 32-bit read-only Processor Version Register (PVR) identifying the processor model in use. The instruction requires supervisor access level.[174]

DSP and transputer-like chip families have not taken up the instruction in any noticeable way, in spite of having (in relative terms) as many variations in design. Alternate ways of silicon identification might be present; for example, DSPs from Texas Instruments contain a memory-based register set for each functional unit that starts with identifiers determining the unit type and model, its ASIC design revision and features selected at the design phase, and continues with unit-specific control and data registers. Access to these areas is performed by simply using the existing load and store instructions; thus, for such devices, there is no need for extending the register set for device identification purposes.[citation needed]

See also[edit]


  1. ^ "Intel 64 and IA-32 Architectures Software Developer's Manual" (PDF). Intel.com. Retrieved 2013-04-11.
  2. ^ "Detecting Intel Processors - Knowing the generation of a system CPU". Rcollins.org. Retrieved 2013-04-11.
  3. ^ "LXR linux-old/arch/i386/kernel/head.S". Lxr.linux.no. Archived from the original on 2012-07-13. Retrieved 2013-04-11.
  4. ^ a b c Debbie Wiles, CPU Identification, archived on 2006-06-04
  5. ^ B-CoolWare, TMi0SDGL x86 CPU/FPU detection library with source code, v2.15, June 2000 - see /SOURCE/REALCODE.ASM for a large collection of pre-CPUID x86 CPU detection routines. Archived on 14 Mar 2023.
  6. ^ "CPUID, EAX=4 - Strange results (Solved)". Software.intel.com. Retrieved 2014-07-10.
  7. ^ @InstLatX64 (February 28, 2019). "First encounter with "GenuineIotel" (o after I, instead of n)" (Tweet) – via Twitter.
  8. ^ "GenuineIotel CPUID dump for Intel Xeon E3-1231". instlatx64.
  9. ^ instlatx64, CPUID dump for RDC IAD 100. Retrieved 22 December 2022.
  10. ^ a b c d smxi, Inxi issue 197: Elbrus CPU support data and implementation. Retrieved 23 October 2023. Archived on 23 October 2023.
  11. ^ Grzegorz Mazur, Identification of x86 CPUs with CPUID support, 5 May 1997. Archived from the original on 24 May 1997.
  12. ^ Ingo Böttcher, CPUDET.PAS v1.61, 23 Oct 1996 - CPU identification program that tests for "AMD ISBETTER" string. Archived on 26 Apr 2024.
  13. ^ sorgelig (Aug 3, 2017). "ao486 CPUID instruction (in commit 43a2004)". GitHub. Archived from the original on 2023-12-04. Retrieved 2023-12-04.
  14. ^ a b sorgelig (Aug 30, 2020). "Update cpuid. · MiSTer-devel/ao486_MiSTer@82f5014". GitHub. Archived from the original on 2023-12-04. Retrieved 2023-12-04.
  15. ^ sorgelig (Aug 30, 2020). "ao486 CPUID instruction". GitHub. Archived from the original on October 23, 2023. Retrieved 4 Dec 2023.
  16. ^ "v586: 586 compatible soft core for FPGA". GitHub. 6 December 2021.
  17. ^ "Steam Hardware & Software Survey". store.steampowered.com. Retrieved 2022-07-26.
  18. ^ "Fun with Timers and cpuid - by Jim Cownie - CPU fun". 3 March 2021.
  19. ^ iXBT Labs, VIA Nano CPUID Tricks, Aug 26, 2010. Archived on Aug 29, 2010.
  20. ^ IDT, WinChip 2A data sheet, v1.0, Jan 1999, page A-3.
  21. ^ VIA, C3 Nehemiah Datasheet, rev 1.13, Sep 29, 2004, page A-3.
  22. ^ Agner Fog, CpuIDFake, v1.00, Jan 22, 2010, see "Instructions.txt". Archived on Jul 9, 2010.
  23. ^ a b Transmeta, Crusoe BIOS Programmer's Guide, Jan 23, 2004, pages 63-65.
  24. ^ Transmeta, Efficeon BIOS Programmers Guide, Aug 19, 2003, section 8.3, page 148.
  25. ^ AMD, Geode LX Data Book, pub.id. 33234H, Feb. 2009, page 107. Archived on Dec 3, 2023.
  26. ^ DM&P, Vortex86EX2_A9133_Master_Data_Sheet_V11_BF, May 8, 2019, page 72.
  27. ^ "Chapter 3 Instruction Set Reference, A-L" (PDF). Intel 64 and IA-32 Architectures Software Developer's Manual. Intel Corporation. 2018-12-20. Retrieved 2018-12-20.
  28. ^ Intel, Pentium Processor Family Developer's Manual, 1997, order no. 241428-005, sections (page 91), 17.5.1 (page 489) and appendix A (page 522) provide more detail on how the "processor type" field and the "dual processor" designation work.
  29. ^ InstLatx64, x86, x64 Instruction Latency, Memory Latency and CPUID dumps, 30 Sep 2023.
  30. ^ AMD, Enhanced Am486DX Microprocessor Family, pub.no. 20736 rev B, March 1997, section 9.2.2, page 55. Archived on 18 Oct 2023.
  31. ^ AMD, ÉlanSC400 and ÉlanSC410 Microcontrollers User's Manual, pub.no. 21030, 1997, section 3.6.2, page 73. Archived on 18 Oct 2023.
  32. ^ Cyrix, 5x86 BIOS Writers Guide, rev 1.12, order no. 92426-00, 1995, page 7
  33. ^ a b Cyrix, CPU Detection Guide, rev 1.01, 2 Oct 1997, page 6.
  34. ^ MiSTer ao486 source code, rtl/ao486/defines.v, line 70. Archived on 23 Oct 2023.
  35. ^ CPU-World, CPUID for Vortex86DX2 933 MHz. Archived on 17 Oct 2023.
  36. ^ CPU-World, CPUID for Vortex86EX2. Archived on 18 Oct 2023.
  37. ^ InstLatx64, Centaur CNS CPUID dump. Archived on 30 May 2023.
  38. ^ Jeff Atwood, Nasty Software Hacks and Intel's CPUID. Coding Horror, 16 Aug 2005.
  39. ^ a b Intel, Intel Xeon Phi Coprocessor Instruction Set Architecture Reference Manual, sep 2012, order no. 327364-001, appendix B.8, pages 673-674. Archived on 4 Aug 2021.
  40. ^ CPU-World, CPUID for Intel Itanium 2 1.50 GHz. Archived on 17 Oct 2023.
  41. ^ InstLatX64, 72-Core Intel Xeon Phi 7290 CPUID dump
  42. ^ InstLatx64, 96-Core AMD Ryzen Threadripper Pro 7995WX CPUID dump
  43. ^ http://bochs.sourceforge.net/techspec/24161821.pdf [bare URL PDF]
  44. ^ Linux 6.3 kernel sources, /arch/x86/include/asm/cpuid.h, line 69
  45. ^ gcc-patches mailing list, CPUID Patch for IDT Winchip, May 21, 2019
  46. ^ Geoff Chappell, CMPXCHG8B Support in the 32-Bit Windows Kernel, Jan 23, 2008. Archived on Jan 30, 2023.
  47. ^ AMD, AMD Processor Recognition Application Note, publication #20734, rev D, Jan 1997, page 13
  48. ^ Intel, AP-485 Application Note - Intel Processor Identification and the CPUID Instruction, order no. 241618-006, march 1997, table 5 on page 10, see bit 10.
  49. ^ Michal Necasek, SYSENTER, Where Are You?, OS/2 Museum, July 20, 2017
  50. ^ Geoff Chappell, ECX From CPUID Leaf 1, Jan 26, 2020. Archived on May 9, 2020.
  51. ^ Huggahalli, Ram; Iyer, Ravi; Tetrick, Scott (2005). "Direct Cache Access for High Bandwidth Network I/O". ACM SIGARCH Computer Architecture News. 33 (2): 50–59. CiteSeerX doi:10.1145/1080695.1069976. CiteSeerX:
  52. ^ Drepper, Ulrich (2007), What Every Programmer Should Know About Memory, CiteSeerX:
  53. ^ a b Intel, Itanium Architecture Software Developer's Manual, rev 2.3, volume 4: IA-32 Instruction Set, may 2010, document number: 323208, table 2-5, page 4:81, see bits 20 and 30. Archived on Feb 15, 2012.
  54. ^ Intel, AP-485, Processor Identification and the CPUID Instruction flag, rev 30, jan 2006, page 26
  55. ^ Michal Necasek, HTT Means Hyper-Threading, Right?, OS/2 Museum, dec 11, 2017
  56. ^ "Mechanisms to determine if software is running in a VMware virtual machine". VMware Knowledge Base. VMWare. 2015-05-01. Intel and AMD CPUs have reserved bit 31 of ECX of CPUID leaf 0x1 as the hypervisor present bit. This bit allows hypervisors to indicate their presence to the guest operating system. Hypervisors set this bit and physical CPUs (all existing and future CPUs) set this bit to zero. Guest operating systems can test bit 31 to detect if they are running inside a virtual machine.
  57. ^ Kataria, Alok; Hecht, Dan (2008-10-01). "Hypervisor CPUID Interface Proposal". LKML Archive on lore.kernel.org. Archived from the original on 2019-03-15. Bit 31 of ECX of CPUID leaf 0x1. This bit has been reserved by Intel & AMD for use by hypervisors and indicates the presence of a hypervisor. Virtual CPU's (hypervisors) set this bit to 1 and physical CPU's (all existing and future CPU's) set this bit to zero. This bit can be probed by the guest software to detect whether they are running inside a virtual machine.
  58. ^ "AMD64 Technology AMD64 Architecture Programmer's Manual Volume 2: System Programming" (PDF) (3.41 ed.). Advanced Micro Devices, Inc. p. 498. 24593. Archived from the original (PDF) on 30 Sep 2023. Retrieved 9 September 2023. 15.2.2 Guest Mode This new processor mode is entered through the VMRUN instruction. When in guest mode, the behavior of some x86 instructions changes to facilitate virtualization. The CPUID function numbers 4000_0000h-4000_00FFh have been reserved for software use. Hypervisors can use these function numbers to provide an interface to pass information from the hypervisor to the guest. This is similar to extracting information about a physical CPU by using CPUID. Hypervisors use the CPUID Fn 400000[FF:00] bit to denote a virtual platform. Feature bit CPUID Fn0000_0001_ECX[31] has been reserved for use by hypervisors to indicate the presence of a hypervisor. Hypervisors set this bit to 1 and physical CPU's set this bit to zero. This bit can be probed by the guest software to detect whether they are running inside a virtual machine.
  59. ^ Intel SDM vol 2A, order no. 253666-053, Jan 2015, p. 244
  60. ^ Intel, Itanium Processor Reference Manual for Software Development, rev 2.0, order no. 245320-003, December 2001, page 110. Archived from the original on 18 Feb 2004.
  61. ^ Intel, Processor Identification and the CPUID Instruction Application Note 485, order no. 241618-036, Aug 2009, page 26. Archived on 6 Oct 2023.
  62. ^ InstLatX64, Willamette-128 CPUID dump. Archived on 7 Dec 2019.
  63. ^ InstlatX64, Intel Atom 230 CPUID dump. Archived on 7 Dec 2019.
  64. ^ WikiChip, Bonnell. Archived on 16 Jul 2017.
  65. ^ Cyrix, Cyrix CPU Detection Guide, rev 1.01, 2 Oct 1997, page 13.
  66. ^ Intel, Processor Identification and the CPUID Instruction Application Note 485, order no. 241618-037, Jan 2011, page 32. Archived on 17 Oct 2023.
  67. ^ Geoff Chappell, CPUID Leaf 2, 26 Jan 2020. Archived on Sep 4, 2023.
  68. ^ Intel, Itanium 2 Processor Reference Manual, order no. 251110-003, May 2004, page 192. Archived from the original on 7 Dec 2006.
  69. ^ Intel, Itanium 2 Processor Specification Update, order.no. 251141-028, Nov 2004, erratum 6 on page 26. Archived from the original on 25 Nov 2004.
  70. ^ Intel, Atom C3000 Processor Product Family Specification Update, order no. 336345-020, page 16, Mar 2023. Archived on 7 Oct 2023.
  71. ^ Intel, Xeon Processor 7500 Series Datasheet, order no. 323341-001, March 2010, page 150. Archived on Oct 8, 2023.
  72. ^ Intel, Optimization Reference Manual, volume 1, order no. 248966-049, jan 2024, chapter, p. 361. Archived on 19 Apr 2024.
  73. ^ a b Shih Kuo (Jan 27, 2012). "Intel 64 Architecture Processor Topology Enumeration".
  74. ^ "Processor and Core Enumeration Using CPUID | AMD". Developer.amd.com. Archived from the original on 2014-07-14. Retrieved 2014-07-10.
  75. ^ "Sandybridge processors report incorrect core number?". Software.intel.com. 2012-12-29. Retrieved 2014-07-10.
  76. ^ "cpuid, __cpuidex". Msdn.microsoft.com. 2014-06-20. Retrieved 2014-07-10.
  77. ^ "x86 architecture - CPUID". sandpile.org. Retrieved 2014-07-10.
  78. ^ "topology.cpp in ps/trunk/source/lib/sysdep/arch/x86_x64 – Wildfire Games". Trac.wildfiregames.com. 2011-12-27. Archived from the original on 2021-03-09. Retrieved 2014-07-10.
  79. ^ Hyper-Threading Technology and Multi-Core Processor Detection
  80. ^ Intel, Architecture Instruction Set Extensions Programming Reference, order no. 319433-052, March 2024, chapter 17. Archived on Apr 7, 2024.
  81. ^ Intel, Intel Processor Identification and the CPUID Instruction (AP-485, rev 30), order no. 241618-030, Jan 2006, page 19.
  82. ^ Intel, Intel 64 and IA-32 Architecture Software Developer's Manual, order no. 352462-079, volume 3B, section, page 3503
  83. ^ Intel, Processor Identification and the CPUID Instruction, order no. 241618-038, apr 2012, p.38
  84. ^ Intel, Product Change Notification 108701, 1 aug 2008. Archived on May 11, 2023
  85. ^ a b "Performance Monitoring Impact of Intel Transactional Synchronization Extension Memory Ordering Issue" (PDF). Intel. June 2023. p. 8. Retrieved 8 May 2024.
  86. ^ a b c Intel, Architecture Specification: Intel Trust Domain Extensions (Intel TDX) Module, order no. 344425-001, sep 2020, pages 120-122. Archived from the original on Jul 29, 2021.
  87. ^ Intel, Deprecating the PCOMMIT instruction, sep 12, 2016. Archived on Apr 23, 2023.
  88. ^ Intel, AVX512-FP16 Architecture Specification (PDF), document number 347407-001, June 2021. Archived on Oct 26, 2022
  89. ^ a b c d "Speculative Execution Side Channel Mitigations" (PDF). Revision 2.0. Intel. May 2018 [January 2018]. Document Number: 336996-002. Retrieved 2018-05-26.
  90. ^ "IBRS patch series [LWN.net]".
  91. ^ a b c Intel, Flexible Return and Event Delivery (FRED) Specification, rev 6.1, December 2023, order no. 346446-007, page 14. Archived on Dec 22, 2023.
  92. ^ Intel, Software Developer's Manual, order no. 325462-080, June 2023 - information about prematurely busy shadow stacks provided in Volume 1, section 17.2.3 on page 410; Volume 2A, table 3.8 (CPUID EAX=7,ECX=2) on page 820; Volume 3C, table 25-14 on page 3958 and section 26.4.3 on page 3984.
  93. ^ LKML, Re: (PATCH v3 00/21) Enable CET Virtualization, Jun 16, 2023 - provides additional discussion of how the CET-SSS prematurely-busy stack issue interacts with virtualization.
  94. ^ a b Intel, Advanced Vector Extensions 10, rev 1.0, July 2023, order no. 355989-001. Archived on Jul 24, 2023.
  95. ^ a b Intel, Advanced Performance Extensions - Architecture Specification, rev 2.0, Aug 2023, order no. 355828-002, page 37. Archived on Sep 10, 2023.
  96. ^ a b c Intel, Branch History Injection and Intra-mode Branch Target Injection / CVE-2022-0001, CVE-2022-0002 / INTEL-SA-00598, 4 Aug 2022. Archived on 5 May 2023.
  97. ^ Intel, Return Stack Buffer Underflow / CVE-2022-29901, CVE-2022-28693 / INTEL-SA-00702, 12 Jul 2022. Archived on 13 Jul 2022.
  98. ^ Intel, Asynchronous Enclave Exit Notify and the EDECCSSA User Leaf Function, 30 Jun 2022. Archived on 21 Nov 2022.
  99. ^ Linux kernel git commit 604dc91, x86/tsc: Use CPUID.0x16 to calculate missing crystal frequency, 9 May 2019 - contains notes on computing the Core Crystal Clock frequency on CPUs that don't specify it, and corresponding C code.
  100. ^ Intel, SDM Volume 3A, order no 253668-083, March 2024, chapter 11.5.4, page 408
  101. ^ instlatx64, Spreadtrum SC9853I-IA CPUID dump
  102. ^ Intel, Architecture Specification: Intel Trust Domain Extensions (Intel TDX) Module, order no. 344425-005, page 93, Feb 2023. Archived on 20 Jul 2023.
  103. ^ a b Microsoft, Hyper-V Feature and Interface Discovery, 8 Jul 2022. Archived on 18 Nov 2023.
  104. ^ Geoff Chappell, HV_HYPERVISOR_INTERFACE, 10 Dec 2022. Archived on 1 Feb 2023.
  105. ^ QEMU documentation, Hyper-V Enlightenments. Archived on 17 Apr 2024.
  106. ^ Linux 6.8.7 kernel source, /source/arch/x86/kvm/cpuid.c, lines 1482-1488
  107. ^ Linux kernel documentation, KVM CPUID bits. Archived on 22 Aug 2022.
  108. ^ Linux 6.8.7 kernel source, /arch/x86/kvm/hyperv.c, line 2793
  109. ^ Linux kernel documentation, Virtualization support: 4.118 KVM_GET_SUPPORTED_HV_CPUID. Archived on 26 Mar 2024.
  110. ^ FreeBSD commit 560d5ed, 28 Jun 2013, see file /sys/amd64/vmm/x86.c, line 48. Archived on 22 Apr 2024.
  111. ^ HyperKit source code, /src/lib/vmm/x86.c line 42, 8 May 2021.
  112. ^ Xen, CPUID Interface to Xen. Archived on 22 Apr 2024.
  113. ^ QEMU source code, fb/target/i386/cpu.c, line 6475, 18 Mar 2024.
  114. ^ VMWare, Mechanisms to determine if software is running in a VMware virtual machine, 1 May 2015. Archived on 18 Jun 2023.
  115. ^ Project ACRN, CPUID Virtualization, 20 Oct 2022. Archived on 25 Mar 2023.
  116. ^ VirtualBox documentation, 9.30 Paravirtualized Debugging. Archived on 22 Apr 2024.
  117. ^ QNX, Hypervisor - Checking the guest's environment, 25 Mar 2022. Archived on 22 Apr 2024.
  118. ^ NetBSD source code, /sys/dev/nvmm/x86/nvmm_x86_vmx.c, line 1430, 6 Nov 2023.
  119. ^ OpenBSD source code, /sys/arch/amd64/include/vmmvar.h, line 24, 9 Apr 2024.
  120. ^ Intel HAXM source code, /core/cpuid.c, line 979, 20 Jan 2023. Archived on 22 Apr 2024.
  121. ^ Intel KGT source code (trusty branch), /vmm/vmexit/vmexit_cpuid.c, lines 17-75, 15 May 2019
  122. ^ Linux kernel v5.18.19 source code, /source/drivers/visorbus/visorchipset.c, line 28
  123. ^ N. Moore, virt: Support detection of LMHS SRE guests #25594, 1 Dec 2022 - Lockheed Martin-provided pull-request for systemd, adding CPUID hypervisor ID string for the LMHS SRE hypervisor. Archived on 23 Apr 2024.
  124. ^ CPUID Specification, publication no.25481, rev 2.34 (PDF), AMD, September 2010, archived from the original (PDF) on 18 Aug 2022
  125. ^ Linux kernel source code
  126. ^ AMD, AMD-K6 Processor Data Sheet, order no. 20695H/0, march 1998, section 24.2, page 283
  127. ^ AMD, AMD-K6 Processor Revision Guide, order no. 21846H/0, June 1999, section 3.2.1, page 17
  128. ^ Intel, Intel 64 and IA-32 Architectures Software Developer's Manual, order no. 325462-079, march 2023, table 3-8 on page 3-238
  129. ^ Lightweight Profiling Specification (PDF), AMD, August 2010, archived from the original (PDF) on 2012-11-27, retrieved 2013-04-03
  130. ^ Cyrix, Cyrix CPU Detection Guide, rev 1.01, oct 2, 1997, page 12
  131. ^ AMD, Geode GX1 Processor Data Book, rev 5.0, december 2003, pages 202 and 226. Archived on 20 Apr 2020.
  132. ^ Transmeta, Processor Recognition, 2002-05-07, page 5
  133. ^ a b AMD, Processor Recognition Application Note, pub.no. 20734, rev. 3.13, december 2005. Section 2.2.2 (p.20) and Section 3 (pages 33 to 40) provide details on how CPUID.(EAX=8000_0001):EDX[bit 19] should be used to identify processors. Section 3 also provides information on AMD's brand name string MSRs. Archived from the original on Jun 26, 2006.
  134. ^ AMD, Family 10h BKDG, document no. 31116, rev 3.62, jan 11, 2013, p. 388 - lists the NodeId bit. Archived on 16 Jan 2019.
  135. ^ AMD, AMD64 Architecture Programmer's Manual Volume 3, pub. no. 24594, rev 3.20, may 2013, page 579 - lists the StreamPerfMon bit
  136. ^ "Intel Processor Identification and the CPUID Instruction" (PDF). Download.intel.com. 2012-03-06. Retrieved 2013-04-11.
  137. ^ InstLatx64, Vortex86DX3 CPUID dump, 27 Sep 2021. Archived on 21 Oct 2021.
  138. ^ InstLatx64, AMD Ryzen 7 6800HS CPUID dump, 21 Feb 2022. Archived on 24 Mar 2023.
  139. ^ Chips and Cheese, Why you can’t trust CPUID, 27 Oct 2022. Archived on 3 Nov 2022.
  140. ^ AMD, Geode LX Databook, pub.id. 33234H, Feb 2009, page 207.
  141. ^ InstLatx64, 2x 24-core Montage Jintide C2460 CPUID dump
  142. ^ InstLatx64, 2x 24-core Intel Xeon Platinum 8160 CPUID dump
  143. ^ InstLatx64, Zhaoxin KaiXian ZX-C+ C4580 CPUID dump
  144. ^ InstLatx64, VIA Eden X4 C4250 CPUID dump
  145. ^ Cyrix, Application Note 112: Cyrix CPU Detection Guide, page 17, 21 July 1998.
  146. ^ Instlatx64, VIA Cyrix III "Samuel" CPUID dump
  147. ^ AMD, BKDG for AMD Family 10h Processors, pub.no. 31116, rev 3.62, jan 11, 2013, page 392. Archived on 16 Jan 2019.
  148. ^ a b c d AMD, PPR For AMD Family 19h Model 61h rev B1 procesors, pub.no. 56713, rev 3.05, Mar 8, 2023, pages 99-100. Archived on 25 Apr 2023.
  149. ^ AMD, BKDG for AMD Family 16h Models 00-0Fh processors, pub.no. 48571, rev 3.03, Feb 19, 2015, page 482. Archived on 16 Jan 2019.
  150. ^ AMD, BIOS and Kernel Developer's Guide for AMD Athlon 64 and AMD Opteron Processors, publication #26094, rev 3.30, feb 2006, pages 29-30 (lists Athlon 64 revision differences, including LMSLE) (archived on 16 Jan 2019), and Revision Guide for AMD Athlon 64 and AMD Opteron Processors, publication #25759, rev 3.79, july 2009, pages 7-8 (lists Athlon 64 revision IDs) (archived on 18 Jan 2019).
  151. ^ AMD, PPR for AMD Family 19h Model 01h, Revision B1 Processors, Volume 1 of 2, document no. 55898, rev 0.50, may 27, 2021, page 98 - lists branch-sampling bit. Archived on Jul 24, 2022
  152. ^ AMD, AMD64 Virtualization Codenamed "Pacifica" Technology, publication no. 33047, rev 3.01, May 2005, appendix B, page 81. Archived on Jun 13, 2011.
  153. ^ AMD, CPUID specification, publication #25481, revision 2.18, jan 2006, page 18.
  154. ^ AMD, CPUID specification, publication #25481, revision 2.34, sep 2010, pages 5 and 11.
  155. ^ Instlatx64, AMD E-350 CPUID dump - has CPUID.(EAX=8000000A):EDX[9] set.
  156. ^ AMD, CPUID specification, publication #25481, revision 2.28, apr 2008, page 21.
  157. ^ AMD, CPUID specification, publication #25481, revision 2.34, sep 2010, page 5 - lists "SseIsa10Compat" as having been dropped in November 2009.
  158. ^ a b AMD, PPR for AMD Family 19h Model 61h, Revision B1 processors, document no. 56713, rev 3.05, mar 8 2023, page 102. Archived on Apr 25, 2023.
  159. ^ AMD, Secure VM Service Module for SEV-SNP Guests, pub.no #58019, rev 1.00, Jul 2023, page 13. Archived on 5 Aug 2023.
  160. ^ a b AMD, PPR for AMD Family 19h Model 61h, Revision B1 processors, document no. 56713, rev 3.05, mar 8 2023, page 116. Archived on Apr 25, 2023.
  161. ^ a b c d e AMD, Technical Update Regarding Speculative Return Stack Overflow, rev 2.0, feb 2024. Archived on Apr 12, 2024.
  162. ^ Ferrie, Peter. "Attacks on Virtual Machine Emulators" (PDF). Symantec. Symantec Advanced Threat Research. Archived from the original (PDF) on 2007-02-07. Retrieved 15 March 2017.
  163. ^ Sandpile, x86 architecture CPUID. Retrieved 22 December 2022.
  164. ^ instlatx64, CPUID dump of AMD A4-5000, lists "HELLO KITTY" string for CPUID leaf 8FFFFFFFh. Retrieved 22 December 2022.
  165. ^ IDT, WinChip 2B Processor Data Sheet, v0.9, April 1999, chapter 3.3.3, page 31.
  166. ^ VIA, PadLock Programming Guide rev. 1.66, aug 4, 2005, page 5. Archived from the original on May 26, 2010
  167. ^ OpenEuler 1.0 LTS kernel sources, /arch/x86/include/asm/cpufeatures.h lines 147-178. Archived on Jul 30, 2023.
  168. ^ VIA, C3 Nehemiah Processor Datasheet, rev 1.13, Sep 29, 2004, page 21
  169. ^ "GCC-mirror/GCC". GitHub. 13 March 2022.
  170. ^ "ARM Information Center". Infocenter.arm.com. Retrieved 2013-04-11.
  171. ^ "Processor version codes and SRM constants". Archived from the original on 2014-09-08. Retrieved 2014-09-08.
  172. ^ a b "IBM System z10 Enterprise Class Technical Guide" (PDF).
  173. ^ "MIPS32 Architecture For Programmers, Volume III: The MIPS32 Privileged Resource Architecture" (PDF). MIPS Technologies, Inc. 2001-03-12.
  174. ^ "PowerPC Operating Environment Architecture, book III" (PDF).

Further reading[edit]

External links[edit]