kernel/trace/rv/monitors/deadline/deadline.c

File Facts

System

Linux kernel

Corpus path

kernel/trace/rv/monitors/deadline/deadline.c

Extension

.c

Size

1122 bytes

Lines

45

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.h
• linux/module.h
• linux/init.h
• linux/rv.h
• linux/kallsyms.h
• deadline.h

Detected Declarations

• function register_deadline
• function unregister_deadline
• module init register_deadline

Annotated Snippet

module_init(register_deadline);
module_exit(unregister_deadline);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Gabriele Monaco <gmonaco@redhat.com>");
MODULE_DESCRIPTION("deadline: container for several deadline scheduler specifications.");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/rv.h`, `linux/kallsyms.h`, `deadline.h`.
• Detected declarations: `function register_deadline`, `function unregister_deadline`, `module init register_deadline`.
• 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.