arch/x86/events/msr.c
Source file repositories/reference/linux-study-clean/arch/x86/events/msr.c
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/events/msr.c- Extension
.c- Size
- 5862 bytes
- Lines
- 244
- Domain
- Architecture Layer
- Bucket
- arch/x86
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/perf_event.hlinux/sysfs.hlinux/nospec.hasm/msr.hprobe.h
Detected Declarations
enum perf_msr_idfunction test_aperfmperffunction test_ptscfunction test_irperffunction test_therm_statusfunction test_intelfunction msr_event_initfunction msr_read_counterfunction msr_event_updatefunction msr_event_startfunction msr_event_stopfunction msr_event_delfunction msr_event_addfunction msr_initmodule init msr_init
Annotated Snippet
device_initcall(msr_init);Annotation
- Immediate include surface: `linux/perf_event.h`, `linux/sysfs.h`, `linux/nospec.h`, `asm/msr.h`, `probe.h`.
- Detected declarations: `enum perf_msr_id`, `function test_aperfmperf`, `function test_ptsc`, `function test_irperf`, `function test_therm_status`, `function test_intel`, `function msr_event_init`, `function msr_read_counter`, `function msr_event_update`, `function msr_event_start`.
- Atlas domain: Architecture Layer / arch/x86.
- Implementation status: integration 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.