arch/arm64/kernel/watchdog_hld.c
Source file repositories/reference/linux-study-clean/arch/arm64/kernel/watchdog_hld.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/kernel/watchdog_hld.c- Extension
.c- Size
- 3078 bytes
- Lines
- 95
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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/nmi.hlinux/cpufreq.hlinux/perf/arm_pmu.h
Detected Declarations
function slowerfunction arch_perf_nmi_is_availablefunction watchdog_perf_update_periodfunction watchdog_freq_notifier_callbackfunction init_watchdog_freq_notifiermodule init init_watchdog_freq_notifier
Annotated Snippet
core_initcall(init_watchdog_freq_notifier);
Annotation
- Immediate include surface: `linux/nmi.h`, `linux/cpufreq.h`, `linux/perf/arm_pmu.h`.
- Detected declarations: `function slower`, `function arch_perf_nmi_is_available`, `function watchdog_perf_update_period`, `function watchdog_freq_notifier_callback`, `function init_watchdog_freq_notifier`, `module init init_watchdog_freq_notifier`.
- Atlas domain: Architecture Layer / arch/arm64.
- 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.