arch/powerpc/perf/vpa-pmu.c
Source file repositories/reference/linux-study-clean/arch/powerpc/perf/vpa-pmu.c
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/perf/vpa-pmu.c- Extension
.c- Size
- 5040 bytes
- Lines
- 206
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- 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/module.hlinux/perf_event.hlinux/sysfs.hasm/kvm_ppc.hasm/kvm_book3s_64.h
Detected Declarations
function Areafunction vpa_pmu_event_initfunction get_counter_datafunction vpa_pmu_addfunction vpa_pmu_readfunction vpa_pmu_delfunction pseries_vpa_pmu_initfunction pseries_vpa_pmu_cleanupmodule init pseries_vpa_pmu_init
Annotated Snippet
module_init(pseries_vpa_pmu_init);
module_exit(pseries_vpa_pmu_cleanup);
MODULE_DESCRIPTION("Perf Driver for pSeries VPA pmu counter");
MODULE_AUTHOR("Kajol Jain <kjain@linux.ibm.com>");
MODULE_AUTHOR("Madhavan Srinivasan <maddy@linux.ibm.com>");
MODULE_LICENSE("GPL");Annotation
- Immediate include surface: `linux/module.h`, `linux/perf_event.h`, `linux/sysfs.h`, `asm/kvm_ppc.h`, `asm/kvm_book3s_64.h`.
- Detected declarations: `function Area`, `function vpa_pmu_event_init`, `function get_counter_data`, `function vpa_pmu_add`, `function vpa_pmu_read`, `function vpa_pmu_del`, `function pseries_vpa_pmu_init`, `function pseries_vpa_pmu_cleanup`, `module init pseries_vpa_pmu_init`.
- Atlas domain: Architecture Layer / arch/powerpc.
- 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.