include/linux/irq_work.h

File Facts

System

Linux kernel

Corpus path

include/linux/irq_work.h

Extension

.h

Size

2007 bytes

Lines

74

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.
• 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

• linux/irq_work_types.h
• linux/rcuwait.h
• linux/smp_types.h
• asm/irq_work.h

Detected Declarations

• function init_irq_work
• function irq_work_is_pending
• function irq_work_is_busy
• function irq_work_is_hard
• function irq_work_needs_cpu
• function irq_work_run

Annotated Snippet

static inline bool irq_work_needs_cpu(void) { return false; }
static inline void irq_work_run(void) { }
static inline void irq_work_single(void *arg) { }
#endif

#endif /* _LINUX_IRQ_WORK_H */

Annotation

• Immediate include surface: `linux/irq_work_types.h`, `linux/rcuwait.h`, `linux/smp_types.h`, `asm/irq_work.h`.
• Detected declarations: `function init_irq_work`, `function irq_work_is_pending`, `function irq_work_is_busy`, `function irq_work_is_hard`, `function irq_work_needs_cpu`, `function irq_work_run`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source 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.