include/linux/sched/isolation.h

File Facts

System

Linux kernel

Corpus path

include/linux/sched/isolation.h

Extension

.h

Size

2522 bytes

Lines

93

Domain

Core OS

Bucket

Core Kernel Interface

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

• linux/cpumask.h
• linux/init.h
• linux/tick.h

Detected Declarations

• enum hk_type
• function housekeeping_any_cpu
• function housekeeping_enabled
• function housekeeping_affine
• function housekeeping_update
• function housekeeping_init
• function cpu_is_isolated

Annotated Snippet

static inline int housekeeping_update(struct cpumask *isol_mask) { return 0; }
static inline void housekeeping_init(void) { }
#endif /* CONFIG_CPU_ISOLATION */

static inline bool housekeeping_cpu(int cpu, enum hk_type type)
{
#ifdef CONFIG_CPU_ISOLATION
	if (static_branch_unlikely(&housekeeping_overridden))
		return housekeeping_test_cpu(cpu, type);
#endif
	return true;
}

static inline bool cpu_is_isolated(int cpu)
{
	return !housekeeping_test_cpu(cpu, HK_TYPE_DOMAIN);
}

#endif /* _LINUX_SCHED_ISOLATION_H */

Annotation

• Immediate include surface: `linux/cpumask.h`, `linux/init.h`, `linux/tick.h`.
• Detected declarations: `enum hk_type`, `function housekeeping_any_cpu`, `function housekeeping_enabled`, `function housekeeping_affine`, `function housekeeping_update`, `function housekeeping_init`, `function cpu_is_isolated`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.