Lines Matching refs:V
8 On arm64, Hyper-V virtualizes the ARMv8 architectural system counter
12 architectural system counter is functional in guest VMs on Hyper-V.
13 While Hyper-V also provides a synthetic system clock and four synthetic
15 Linux kernel in a Hyper-V guest on arm64. However, older versions
16 of Hyper-V for arm64 only partially virtualize the ARMv8
19 Linux kernel versions on these older Hyper-V versions requires an
20 out-of-tree patch to use the Hyper-V synthetic clocks/timers instead.
24 On x86/x64, Hyper-V provides guest VMs with a synthetic system clock
25 and four synthetic per-CPU timers as described in the TLFS. Hyper-V
29 Hyper-V performs TSC calibration, and provides the TSC frequency
30 to the guest VM via a synthetic MSR. Hyper-V initialization code
32 calibration and sets tsc_reliable. Hyper-V provides virtualized
33 versions of the PIT (in Hyper-V Generation 1 VMs only), local
34 APIC timer, and RTC. Hyper-V does not provide a virtualized HPET in
37 The Hyper-V synthetic system clock can be read via a synthetic MSR,
40 and the hypervisor. Hyper-V populates this memory page with a
43 as described in the Hyper-V TLFS. The resulting value advances
45 to a host with a different TSC frequency, Hyper-V adjusts the
49 Starting with Windows Server 2022 Hyper-V, Hyper-V uses hardware
51 across Hyper-V hosts where the TSC frequency may be different.
52 When a Linux guest detects that this Hyper-V functionality is
54 Otherwise, it uses the clocksource for the Hyper-V synthetic system
58 The Hyper-V synthetic system clock is available to user space via
65 Linux clockevents are based on Hyper-V synthetic timer 0. While
66 Hyper-V offers 4 synthetic timers for each CPU, Linux only uses
69 local APIC timer also work, but the Hyper-V synthetic timer is
72 The driver for the Hyper-V synthetic system clock and timers is