tools/power/cpupower/debug/kernel/cpufreq-test_tsc.c
Source file repositories/reference/linux-study-clean/tools/power/cpupower/debug/kernel/cpufreq-test_tsc.c
File Facts
- System
- Linux kernel
- Corpus path
tools/power/cpupower/debug/kernel/cpufreq-test_tsc.c- Extension
.c- Size
- 3124 bytes
- Lines
- 112
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
Dependency Surface
linux/kernel.hlinux/module.hlinux/init.hlinux/delay.hlinux/acpi.hasm/io.h
Detected Declarations
function read_pmtmrfunction cpufreq_test_tscfunction cpufreq_nonemodule init cpufreq_test_tsc
Annotated Snippet
module_init(cpufreq_test_tsc)
module_exit(cpufreq_none)
MODULE_AUTHOR("Dominik Brodowski");
MODULE_DESCRIPTION("Verify the TSC cpufreq notifier working correctly -- needs ACPI-enabled system");
MODULE_LICENSE ("GPL");Annotation
- Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/delay.h`, `linux/acpi.h`, `asm/io.h`.
- Detected declarations: `function read_pmtmr`, `function cpufreq_test_tsc`, `function cpufreq_none`, `module init cpufreq_test_tsc`.
- Atlas domain: Support Tooling And Documentation / tools.
- 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.