kernel/trace/rv/monitors/sleep/Kconfig

File Facts

System

Linux kernel

Corpus path

kernel/trace/rv/monitors/sleep/Kconfig

Extension

[no extension]

Size

658 bytes

Lines

23

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

Inferred role

Core OS: build/configuration rule

Status

atlas-only

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.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
#
config RV_MON_SLEEP
	depends on RV
	select RV_LTL_MONITOR
	depends on HAVE_SYSCALL_TRACEPOINTS
	depends on RV_MON_RTAPP
	select TRACE_IRQFLAGS
	default y
	select LTL_MON_EVENTS_ID
	bool "sleep monitor"
	help
	  Monitor that real-time tasks do not sleep in a manner that may
	  cause undesirable latency.

	  If you are developing a real-time system and not entirely sure whether
	  the applications are designed correctly for real-time, you want to say
	  Y here.

	  Enabling this monitor may have performance impact (due to select
	  TRACE_IRQFLAGS). Therefore, you probably should say N for
	  production kernel.

Annotation

• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• Implementation status: atlas-only.

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.