kernel/trace/rv/monitors/wwnr/wwnr.c

Source file repositories/reference/linux-study-clean/kernel/trace/rv/monitors/wwnr/wwnr.c

File Facts

System: Linux kernel
Corpus path: kernel/trace/rv/monitors/wwnr/wwnr.c
Extension: .c
Size: 1892 bytes
Lines: 85
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/ftrace.h
linux/tracepoint.h
linux/kernel.h
linux/module.h
linux/init.h
linux/rv.h
rv/instrumentation.h
rv_trace.h
trace/events/sched.h
wwnr.h
rv/da_monitor.h

Detected Declarations

function handle_switch
function handle_wakeup
function enable_wwnr
function disable_wwnr
function register_wwnr
function unregister_wwnr
module init register_wwnr

Annotated Snippet

module_init(register_wwnr);
module_exit(unregister_wwnr);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Daniel Bristot de Oliveira <bristot@kernel.org>");
MODULE_DESCRIPTION("wwnr: wakeup while not running monitor");

Annotation

Immediate include surface: `linux/ftrace.h`, `linux/tracepoint.h`, `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/rv.h`, `rv/instrumentation.h`, `rv_trace.h`.
Detected declarations: `function handle_switch`, `function handle_wakeup`, `function enable_wwnr`, `function disable_wwnr`, `function register_wwnr`, `function unregister_wwnr`, `module init register_wwnr`.
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.