kernel/trace/rv/monitors/nrp/nrp.h

File Facts

System

Linux kernel

Corpus path

kernel/trace/rv/monitors/nrp/nrp.h

Extension

.h

Size

1524 bytes

Lines

78

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_nrp
• enum states_nrp
• enum events_nrp

Annotated Snippet

struct automaton_nrp {
	char *state_names[state_max_nrp];
	char *event_names[event_max_nrp];
	unsigned char function[state_max_nrp][event_max_nrp];
	unsigned char initial_state;
	bool final_states[state_max_nrp];
};

static const struct automaton_nrp automaton_nrp = {
	.state_names = {
		"preempt_irq",
		"any_thread_running",
		"nested_preempt",
		"rescheduling",
	},
	.event_names = {
		"irq_entry",
		"sched_need_resched",
		"schedule_entry",
		"schedule_entry_preempt",
	},
	.function = {
		{
			preempt_irq_nrp,
			preempt_irq_nrp,
			nested_preempt_nrp,
			nested_preempt_nrp,
		},
		{
			any_thread_running_nrp,
			rescheduling_nrp,
			any_thread_running_nrp,
			INVALID_STATE,
		},
		{
			nested_preempt_nrp,
			preempt_irq_nrp,
			any_thread_running_nrp,
			any_thread_running_nrp,
		},
		{
			preempt_irq_nrp,
			rescheduling_nrp,
			any_thread_running_nrp,
			any_thread_running_nrp,
		},
	},
	.initial_state = preempt_irq_nrp,
	.final_states = { 0, 1, 0, 0 },
};

Annotation

• Detected declarations: `struct automaton_nrp`, `enum states_nrp`, `enum events_nrp`.
• 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.