kernel/power/poweroff.c
Source file repositories/reference/linux-study-clean/kernel/power/poweroff.c
File Facts
- System
- Linux kernel
- Corpus path
kernel/power/poweroff.c- Extension
.c- Size
- 991 bytes
- Lines
- 46
- Domain
- Core OS
- Bucket
- Scheduler, Processes, Timers, Sync, And Syscalls
- Inferred role
- Core OS: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- 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/kernel.hlinux/sysrq.hlinux/init.hlinux/pm.hlinux/workqueue.hlinux/reboot.hlinux/cpumask.h
Detected Declarations
function do_powerofffunction handle_powerofffunction pm_sysrq_initmodule init pm_sysrq_init
Annotated Snippet
subsys_initcall(pm_sysrq_init);Annotation
- Immediate include surface: `linux/kernel.h`, `linux/sysrq.h`, `linux/init.h`, `linux/pm.h`, `linux/workqueue.h`, `linux/reboot.h`, `linux/cpumask.h`.
- Detected declarations: `function do_poweroff`, `function handle_poweroff`, `function pm_sysrq_init`, `module init pm_sysrq_init`.
- Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
- 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.