kernel/sched/build_utility.c
Source file repositories/reference/linux-study-clean/kernel/sched/build_utility.c
File Facts
- System
- Linux kernel
- Corpus path
kernel/sched/build_utility.c- Extension
.c- Size
- 2325 bytes
- Lines
- 107
- 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.
Dependency Surface
linux/sched/clock.hlinux/sched/cputime.hlinux/sched/debug.hlinux/sched/isolation.hlinux/sched/loadavg.hlinux/sched/nohz.hlinux/sched/mm.hlinux/sched/rseq_api.hlinux/sched/task_stack.hlinux/cpufreq.hlinux/cpumask_api.hlinux/cpuset.hlinux/ctype.hlinux/debugfs.hlinux/energy_model.hlinux/hashtable_api.hlinux/irq.hlinux/kobject_api.hlinux/membarrier.hlinux/mempolicy.hlinux/nmi.hlinux/nospec.hlinux/proc_fs.hlinux/psi.hlinux/ptrace_api.hlinux/sched_clock.hlinux/security.hlinux/spinlock_api.hlinux/swait_api.hlinux/timex.hlinux/utsname.hlinux/wait_api.h
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
/*
* These are various utility functions of the scheduler,
* built in a single compilation unit for build efficiency reasons.
*
* ( Incidentally, the size of the compilation unit is roughly
* comparable to core.c, fair.c, smp.c and policy.c, the other
* big compilation units. This helps balance build time, while
* coalescing source files to amortize header inclusion
* cost. )
*/
#include <linux/sched/clock.h>
#include <linux/sched/cputime.h>
#include <linux/sched/debug.h>
#include <linux/sched/isolation.h>
#include <linux/sched/loadavg.h>
#include <linux/sched/nohz.h>
#include <linux/sched/mm.h>
#include <linux/sched/rseq_api.h>
#include <linux/sched/task_stack.h>
#include <linux/cpufreq.h>
#include <linux/cpumask_api.h>
#include <linux/cpuset.h>
#include <linux/ctype.h>
#include <linux/debugfs.h>
#include <linux/energy_model.h>
#include <linux/hashtable_api.h>
#include <linux/irq.h>
#include <linux/kobject_api.h>
#include <linux/membarrier.h>
#include <linux/mempolicy.h>
#include <linux/nmi.h>
#include <linux/nospec.h>
#include <linux/proc_fs.h>
#include <linux/psi.h>
#include <linux/ptrace_api.h>
#include <linux/sched_clock.h>
#include <linux/security.h>
#include <linux/spinlock_api.h>
#include <linux/swait_api.h>
#include <linux/timex.h>
#include <linux/utsname.h>
#include <linux/wait_api.h>
#include <linux/workqueue_api.h>
#include <uapi/linux/prctl.h>
#include <uapi/linux/sched/types.h>
#include <asm/switch_to.h>
#include "sched.h"
#include "sched-pelt.h"
#include "stats.h"
#include "autogroup.h"
#include "clock.c"
#ifdef CONFIG_CGROUP_CPUACCT
# include "cpuacct.c"
#endif
#ifdef CONFIG_CPU_FREQ
# include "cpufreq.c"
#endif
#ifdef CONFIG_CPU_FREQ_GOV_SCHEDUTIL
# include "cpufreq_schedutil.c"
#endif
#include "debug.c"
#ifdef CONFIG_SCHEDSTATS
# include "stats.c"
#endif
#include "loadavg.c"
#include "completion.c"
#include "swait.c"
#include "wait_bit.c"
#include "wait.c"
#include "cpupri.c"
#include "stop_task.c"
#include "topology.c"
#ifdef CONFIG_SCHED_CORE
# include "core_sched.c"
#endif
Annotation
- Immediate include surface: `linux/sched/clock.h`, `linux/sched/cputime.h`, `linux/sched/debug.h`, `linux/sched/isolation.h`, `linux/sched/loadavg.h`, `linux/sched/nohz.h`, `linux/sched/mm.h`, `linux/sched/rseq_api.h`.
- 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.