arch/um/drivers/harddog_user_exp.c
Source file repositories/reference/linux-study-clean/arch/um/drivers/harddog_user_exp.c
File Facts
- System
- Linux kernel
- Corpus path
arch/um/drivers/harddog_user_exp.c- Extension
.c- Size
- 217 bytes
- Lines
- 10
- Domain
- Architecture Layer
- Bucket
- arch/um
- 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.
Dependency Surface
linux/export.hharddog.h
Detected Declarations
export start_watchdogexport stop_watchdogexport ping_watchdog
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include <linux/export.h>
#include "harddog.h"
#if IS_MODULE(CONFIG_UML_WATCHDOG)
EXPORT_SYMBOL(start_watchdog);
EXPORT_SYMBOL(stop_watchdog);
EXPORT_SYMBOL(ping_watchdog);
#endif
Annotation
- Immediate include surface: `linux/export.h`, `harddog.h`.
- Detected declarations: `export start_watchdog`, `export stop_watchdog`, `export ping_watchdog`.
- Atlas domain: Architecture Layer / arch/um.
- 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.