arch/x86/include/asm/asm-prototypes.h
Source file repositories/reference/linux-study-clean/arch/x86/include/asm/asm-prototypes.h
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/include/asm/asm-prototypes.h- Extension
.h- Size
- 550 bytes
- Lines
- 26
- 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
asm/ftrace.hlinux/uaccess.hlinux/pgtable.hasm/string.hasm/page.hasm/checksum.hasm/mce.hasm-generic/asm-prototypes.hasm/special_insns.hasm/preempt.hasm/asm.hasm/fred.hasm/gsseg.hasm/nospec-branch.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#include <asm/ftrace.h>
#include <linux/uaccess.h>
#include <linux/pgtable.h>
#include <asm/string.h>
#include <asm/page.h>
#include <asm/checksum.h>
#include <asm/mce.h>
#include <asm-generic/asm-prototypes.h>
#include <asm/special_insns.h>
#include <asm/preempt.h>
#include <asm/asm.h>
#include <asm/fred.h>
#include <asm/gsseg.h>
#include <asm/nospec-branch.h>
#ifndef CONFIG_X86_CX8
extern void cmpxchg8b_emu(void);
#endif
#ifdef CONFIG_STACKPROTECTOR
extern unsigned long __ref_stack_chk_guard;
#endif
Annotation
- Immediate include surface: `asm/ftrace.h`, `linux/uaccess.h`, `linux/pgtable.h`, `asm/string.h`, `asm/page.h`, `asm/checksum.h`, `asm/mce.h`, `asm-generic/asm-prototypes.h`.
- 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.