arch/x86/include/asm/pvclock.h

File Facts

System

Linux kernel

Corpus path

arch/x86/include/asm/pvclock.h

Extension

.h

Size

2801 bytes

Lines

109

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/clocksource.h
• asm/pvclock-abi.h

Detected Declarations

• struct timespec64
• struct pvclock_vsyscall_time_info
• function pvclock_read_begin
• function pvclock_read_retry
• function pvclock_scale_delta
• function __pvclock_read_cycles

Annotated Snippet

struct pvclock_vsyscall_time_info {
	struct pvclock_vcpu_time_info pvti;
} __attribute__((__aligned__(SMP_CACHE_BYTES)));

#define PVTI_SIZE sizeof(struct pvclock_vsyscall_time_info)

#ifdef CONFIG_PARAVIRT_CLOCK
void pvclock_set_pvti_cpu0_va(struct pvclock_vsyscall_time_info *pvti);
struct pvclock_vsyscall_time_info *pvclock_get_pvti_cpu0_va(void);
#else
static inline struct pvclock_vsyscall_time_info *pvclock_get_pvti_cpu0_va(void)
{
	return NULL;
}
#endif

#endif /* _ASM_X86_PVCLOCK_H */

Annotation

• Immediate include surface: `asm/clocksource.h`, `asm/pvclock-abi.h`.
• Detected declarations: `struct timespec64`, `struct pvclock_vsyscall_time_info`, `function pvclock_read_begin`, `function pvclock_read_retry`, `function pvclock_scale_delta`, `function __pvclock_read_cycles`.
• 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.