include/clocksource/hyperv_timer.h

File Facts

System

Linux kernel

Corpus path

include/clocksource/hyperv_timer.h

Extension

.h

Size

3350 bytes

Lines

118

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/clocksource.h
• linux/math64.h
• hyperv/hvhdk.h
• asm/hyperv_timer.h

Detected Declarations

• function hv_read_tsc_page_tsc
• function hv_get_tsc_pfn
• function hv_read_tsc_page_tsc
• function hv_stimer_cleanup
• function hv_stimer_legacy_init

Annotated Snippet

static inline int hv_stimer_cleanup(unsigned int cpu) { return 0; }
static inline void hv_stimer_legacy_init(unsigned int cpu, int sint) {}
static inline void hv_stimer_legacy_cleanup(unsigned int cpu) {}
static inline void hv_stimer_global_cleanup(void) {}
static inline void hv_stimer0_isr(void) {}

#endif /* CONFIG_HYPERV_TIMER */

#endif

Annotation

• Immediate include surface: `linux/clocksource.h`, `linux/math64.h`, `hyperv/hvhdk.h`, `asm/hyperv_timer.h`.
• Detected declarations: `function hv_read_tsc_page_tsc`, `function hv_get_tsc_pfn`, `function hv_read_tsc_page_tsc`, `function hv_stimer_cleanup`, `function hv_stimer_legacy_init`.
• Atlas domain: Repository Root And Misc / include.
• 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.