include/linux/hrtimer_rearm.h

File Facts

System

Linux kernel

Corpus path

include/linux/hrtimer_rearm.h

Extension

.h

Size

2727 bytes

Lines

84

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.

Dependency Surface

• linux/thread_info.h

Detected Declarations

• function test_and_clear_bit
• function hrtimer_rearm_deferred_user_irq
• function hrtimer_rearm_deferred_tif
• function irqentry_exit
• function __schedule
• function __hrtimer_rearm_deferred
• function hrtimer_test_and_clear_rearm_deferred

Annotated Snippet

static __always_inline void __hrtimer_rearm_deferred(void) { }
static __always_inline void hrtimer_rearm_deferred(void) { }
static __always_inline void hrtimer_rearm_deferred_tif(unsigned long tif_work) { }
static __always_inline bool
hrtimer_rearm_deferred_user_irq(unsigned long *tif_work, const unsigned long tif_mask) { return false; }
static __always_inline bool hrtimer_test_and_clear_rearm_deferred(void) { return false; }
#endif  /* !CONFIG_HRTIMER_REARM_DEFERRED */

#endif

Annotation

• Immediate include surface: `linux/thread_info.h`.
• Detected declarations: `function test_and_clear_bit`, `function hrtimer_rearm_deferred_user_irq`, `function hrtimer_rearm_deferred_tif`, `function irqentry_exit`, `function __schedule`, `function __hrtimer_rearm_deferred`, `function hrtimer_test_and_clear_rearm_deferred`.
• 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.