kernel/sched/stats.c

File Facts

System

Linux kernel

Corpus path

kernel/sched/stats.c

Extension

.c

Size

5402 bytes

Lines

221

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• sched.h

Detected Declarations

• function __update_stats_wait_start
• function __update_stats_wait_end
• function __update_stats_enqueue_sleeper
• function show_schedstat
• function for_each_domain
• function schedstat_stop
• function proc_schedstat_init
• module init proc_schedstat_init

Annotated Snippet

subsys_initcall(proc_schedstat_init);

Annotation

• Immediate include surface: `sched.h`.
• Detected declarations: `function __update_stats_wait_start`, `function __update_stats_wait_end`, `function __update_stats_enqueue_sleeper`, `function show_schedstat`, `function for_each_domain`, `function schedstat_stop`, `function proc_schedstat_init`, `module init proc_schedstat_init`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.