arch/x86/include/asm/intel-family.h
Source file repositories/reference/linux-study-clean/arch/x86/include/asm/intel-family.h
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/include/asm/intel-family.h- Extension
.h- Size
- 8344 bytes
- Lines
- 230
- Domain
- Architecture Layer
- Bucket
- arch/x86
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
enum intel_cpu_typeenum intel_native_id
Annotated Snippet
#ifndef _ASM_X86_INTEL_FAMILY_H
#define _ASM_X86_INTEL_FAMILY_H
/*
* "Big Core" Processors (Branded as Core, Xeon, etc...)
*
* While adding a new CPUID for a new microarchitecture, add a new
* group to keep logically sorted out in chronological order. Within
* that group keep the CPUID for the variants sorted by model number.
*
* The defined symbol names have the following form:
* INTEL_{OPTFAMILY}_{MICROARCH}{OPTDIFF}
* where:
* OPTFAMILY Describes the family of CPUs that this belongs to. Default
* is assumed to be "_CORE" (and should be omitted). Other values
* currently in use are _ATOM and _XEON_PHI
* MICROARCH Is the code name for the micro-architecture for this core.
* N.B. Not the platform name.
* OPTDIFF If needed, a short string to differentiate by market segment.
*
* Common OPTDIFFs:
*
* - regular client parts
* _L - regular mobile parts
* _G - parts with extra graphics on
* _X - regular server parts
* _D - micro server parts
* _N,_P - other mobile parts
* _H - premium mobile parts
* _S - other client parts
* _R - ruggedized for harsh environment
*
* Historical OPTDIFFs:
*
* _EP - 2 socket server parts
* _EX - 4+ socket server parts
*
* The #define line may optionally include a comment including platform or core
* names. An exception is made for skylake/kabylake where steppings seem to have gotten
* their own names :-(
*/
#define IFM(_fam, _model) VFM_MAKE(X86_VENDOR_INTEL, _fam, _model)
/* Wildcard match so X86_MATCH_VFM(ANY) works */
#define INTEL_ANY IFM(X86_FAMILY_ANY, X86_MODEL_ANY)
/* Family 5 */
#define INTEL_FAM5_START IFM(5, 0x00) /* Notational marker, also P5 A-step */
#define INTEL_PENTIUM_75 IFM(5, 0x02) /* P54C */
#define INTEL_PENTIUM_MMX IFM(5, 0x04) /* P55C */
#define INTEL_QUARK_X1000 IFM(5, 0x09) /* Quark X1000 SoC */
/* Family 6, 18, 19 */
#define INTEL_PENTIUM_PRO IFM(6, 0x01)
#define INTEL_PENTIUM_II_KLAMATH IFM(6, 0x03)
#define INTEL_PENTIUM_III_DESCHUTES IFM(6, 0x05)
#define INTEL_PENTIUM_III_TUALATIN IFM(6, 0x0B)
#define INTEL_PENTIUM_M_DOTHAN IFM(6, 0x0D)
#define INTEL_CORE_YONAH IFM(6, 0x0E)
#define INTEL_CORE2_MEROM IFM(6, 0x0F)
#define INTEL_CORE2_MEROM_L IFM(6, 0x16)
#define INTEL_CORE2_PENRYN IFM(6, 0x17)
#define INTEL_CORE2_DUNNINGTON IFM(6, 0x1D)
#define INTEL_NEHALEM IFM(6, 0x1E)
#define INTEL_NEHALEM_G IFM(6, 0x1F) /* Auburndale / Havendale */
#define INTEL_NEHALEM_EP IFM(6, 0x1A)
#define INTEL_NEHALEM_EX IFM(6, 0x2E)
#define INTEL_WESTMERE IFM(6, 0x25)
#define INTEL_WESTMERE_EP IFM(6, 0x2C)
#define INTEL_WESTMERE_EX IFM(6, 0x2F)
#define INTEL_SANDYBRIDGE IFM(6, 0x2A)
#define INTEL_SANDYBRIDGE_X IFM(6, 0x2D)
#define INTEL_IVYBRIDGE IFM(6, 0x3A)
#define INTEL_IVYBRIDGE_X IFM(6, 0x3E)
#define INTEL_HASWELL IFM(6, 0x3C)
#define INTEL_HASWELL_X IFM(6, 0x3F)
#define INTEL_HASWELL_L IFM(6, 0x45)
#define INTEL_HASWELL_G IFM(6, 0x46)
#define INTEL_BROADWELL IFM(6, 0x3D)
#define INTEL_BROADWELL_G IFM(6, 0x47)
#define INTEL_BROADWELL_X IFM(6, 0x4F)
#define INTEL_BROADWELL_D IFM(6, 0x56)
Annotation
- Detected declarations: `enum intel_cpu_type`, `enum intel_native_id`.
- Atlas domain: Architecture Layer / arch/x86.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.