arch/x86/include/asm/mpspec.h
Source file repositories/reference/linux-study-clean/arch/x86/include/asm/mpspec.h
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/include/asm/mpspec.h- Extension
.h- Size
- 1901 bytes
- Lines
- 78
- 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
linux/types.hasm/mpspec_def.hasm/x86_init.hasm/apicdef.h
Detected Declarations
function e820__memblock_alloc_reserved_mpc_newfunction reset_phys_cpu_present_mapfunction copy_phys_cpu_present_map
Annotated Snippet
static inline void e820__memblock_alloc_reserved_mpc_new(void) { }
#define enable_update_mptable 0
#define mpparse_find_mptable x86_init_noop
#define mpparse_parse_early_smp_config x86_init_noop
#define mpparse_parse_smp_config x86_init_noop
#endif
extern DECLARE_BITMAP(phys_cpu_present_map, MAX_LOCAL_APIC);
static inline void reset_phys_cpu_present_map(u32 apicid)
{
bitmap_zero(phys_cpu_present_map, MAX_LOCAL_APIC);
set_bit(apicid, phys_cpu_present_map);
}
static inline void copy_phys_cpu_present_map(unsigned long *dst)
{
bitmap_copy(dst, phys_cpu_present_map, MAX_LOCAL_APIC);
}
#endif /* _ASM_X86_MPSPEC_H */
Annotation
- Immediate include surface: `linux/types.h`, `asm/mpspec_def.h`, `asm/x86_init.h`, `asm/apicdef.h`.
- Detected declarations: `function e820__memblock_alloc_reserved_mpc_new`, `function reset_phys_cpu_present_map`, `function copy_phys_cpu_present_map`.
- 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.