kernel/trace/rv/monitors/scpd/scpd.h
Source file repositories/reference/linux-study-clean/kernel/trace/rv/monitors/scpd/scpd.h
File Facts
- System
- Linux kernel
- Corpus path
kernel/trace/rv/monitors/scpd/scpd.h- Extension
.h- Size
- 1188 bytes
- Lines
- 52
- Domain
- Core OS
- Bucket
- Scheduler, Processes, Timers, Sync, And Syscalls
- Inferred role
- Core OS: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
struct automaton_scpdenum states_scpdenum events_scpd
Annotated Snippet
struct automaton_scpd {
char *state_names[state_max_scpd];
char *event_names[event_max_scpd];
unsigned char function[state_max_scpd][event_max_scpd];
unsigned char initial_state;
bool final_states[state_max_scpd];
};
static const struct automaton_scpd automaton_scpd = {
.state_names = {
"cant_sched",
"can_sched",
},
.event_names = {
"preempt_disable",
"preempt_enable",
"schedule_entry",
"schedule_exit",
},
.function = {
{ can_sched_scpd, INVALID_STATE, INVALID_STATE, INVALID_STATE },
{ INVALID_STATE, cant_sched_scpd, can_sched_scpd, can_sched_scpd },
},
.initial_state = cant_sched_scpd,
.final_states = { 1, 0 },
};
Annotation
- Detected declarations: `struct automaton_scpd`, `enum states_scpd`, `enum events_scpd`.
- Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
- Implementation status: source 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.