arch/sparc/kernel/sysfs.c
Source file repositories/reference/linux-study-clean/arch/sparc/kernel/sysfs.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sparc/kernel/sysfs.c- Extension
.c- Size
- 7987 bytes
- Lines
- 266
- Domain
- Architecture Layer
- Bucket
- arch/sparc
- 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/sched.hlinux/device.hlinux/cpu.hlinux/smp.hlinux/percpu.hlinux/init.hasm/cpudata.hasm/hypervisor.hasm/spitfire.h
Detected Declarations
function read_mmustat_enablefunction write_mmustat_enablefunction show_mmustat_enablefunction store_mmustat_enablefunction register_mmu_statsfunction unregister_mmu_statsfunction register_cpu_onlinefunction unregister_cpu_onlinefunction check_mmu_statsfunction topology_initfunction for_each_possible_cpumodule init topology_init
Annotated Snippet
subsys_initcall(topology_init);Annotation
- Immediate include surface: `linux/sched.h`, `linux/device.h`, `linux/cpu.h`, `linux/smp.h`, `linux/percpu.h`, `linux/init.h`, `asm/cpudata.h`, `asm/hypervisor.h`.
- Detected declarations: `function read_mmustat_enable`, `function write_mmustat_enable`, `function show_mmustat_enable`, `function store_mmustat_enable`, `function register_mmu_stats`, `function unregister_mmu_stats`, `function register_cpu_online`, `function unregister_cpu_online`, `function check_mmu_stats`, `function topology_init`.
- Atlas domain: Architecture Layer / arch/sparc.
- 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.