arch/x86/include/asm/clock_inlined.h
Source file repositories/reference/linux-study-clean/arch/x86/include/asm/clock_inlined.h
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/include/asm/clock_inlined.h- Extension
.h- Size
- 465 bytes
- Lines
- 23
- Domain
- Architecture Layer
- Bucket
- arch/x86
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
asm/tsc.h
Detected Declarations
struct clocksourcestruct clock_event_devicefunction arch_inlined_clocksource_readfunction arch_inlined_clockevent_set_next_coupled
Annotated Snippet
#ifndef _ASM_X86_CLOCK_INLINED_H
#define _ASM_X86_CLOCK_INLINED_H
#include <asm/tsc.h>
struct clocksource;
static __always_inline u64 arch_inlined_clocksource_read(struct clocksource *cs)
{
return (u64)rdtsc_ordered();
}
struct clock_event_device;
static __always_inline void
arch_inlined_clockevent_set_next_coupled(u64 cycles, struct clock_event_device *evt)
{
native_wrmsrq(MSR_IA32_TSC_DEADLINE, cycles);
}
#endif
Annotation
- Immediate include surface: `asm/tsc.h`.
- Detected declarations: `struct clocksource`, `struct clock_event_device`, `function arch_inlined_clocksource_read`, `function arch_inlined_clockevent_set_next_coupled`.
- Atlas domain: Architecture Layer / arch/x86.
- 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.