kernel/rcu/tasks.h
Source file repositories/reference/linux-study-clean/kernel/rcu/tasks.h
File Facts
- System
- Linux kernel
- Corpus path
kernel/rcu/tasks.h- Extension
.h- Size
- 54409 bytes
- Lines
- 1610
- 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.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
rcu_segcblist.h
Detected Declarations
struct rcu_tasksstruct rcu_tasks_percpustruct rcu_tasksstruct rcu_tasks_test_descfunction set_tasks_gp_statefunction cblist_init_genericfunction for_each_possible_cpufunction rcu_tasks_lazy_timefunction call_rcu_tasks_generic_timerfunction call_rcu_tasks_iw_wakeupfunction call_rcu_tasks_genericfunction rcu_barrier_tasks_generic_cbfunction rcu_barrier_tasks_genericfunction rcu_tasks_need_gpcbfunction rcu_tasks_invoke_cbsfunction rcu_tasks_invoke_cbs_wqfunction rcu_tasks_one_gpfunction rcu_tasks_kthreadfunction for_each_possible_cpufunction synchronize_rcu_tasks_genericfunction rcu_spawn_tasks_kthread_genericfunction rcu_tasks_bootup_oddnessfunction show_rcu_tasks_generic_gp_kthreadfunction for_each_possible_cpufunction rcu_tasks_torture_stats_print_genericfunction rcu_tasks_wait_gpfunction rcu_tasks_pregp_stepfunction rcu_tasks_is_holdoutfunction rcu_tasks_pertaskfunction rcu_tasks_postscanfunction schedulefunction list_for_each_entry_safefunction check_holdout_taskfunction check_all_holdout_tasksfunction list_for_each_entry_safefunction rcu_tasks_postgpfunction tasks_rcu_exit_srcu_stallfunction call_rcu_tasksfunction cond_resched_tasks_rcu_qsfunction rcu_barrier_tasksfunction rcu_spawn_tasks_kthreadfunction show_rcu_tasks_classic_gp_kthreadfunction rcu_tasks_torture_stats_printfunction rcu_tasks_get_gp_datafunction get_task_structfunction exit_tasks_rcu_finishfunction exit_tasks_rcu_startfunction call_rcu_tasks_rude
Annotated Snippet
core_initcall(rcu_init_tasks_generic);
#else /* #ifdef CONFIG_TASKS_RCU_GENERIC */
static inline void rcu_tasks_bootup_oddness(void) {}
#endif /* #else #ifdef CONFIG_TASKS_RCU_GENERIC */
#ifdef CONFIG_TASKS_TRACE_RCU
////////////////////////////////////////////////////////////////////////
//
// Tracing variant of Tasks RCU. This variant is designed to be used
// to protect tracing hooks, including those of BPF. This variant
// is implemented via a straightforward mapping onto SRCU-fast.
DEFINE_SRCU_FAST(rcu_tasks_trace_srcu_struct);
EXPORT_SYMBOL_GPL(rcu_tasks_trace_srcu_struct);
#endif /* #else #ifdef CONFIG_TASKS_TRACE_RCU */
Annotation
- Immediate include surface: `rcu_segcblist.h`.
- Detected declarations: `struct rcu_tasks`, `struct rcu_tasks_percpu`, `struct rcu_tasks`, `struct rcu_tasks_test_desc`, `function set_tasks_gp_state`, `function cblist_init_generic`, `function for_each_possible_cpu`, `function rcu_tasks_lazy_time`, `function call_rcu_tasks_generic_timer`, `function call_rcu_tasks_iw_wakeup`.
- 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.