On Tue, 28 Jul 2026 15:39:40 +0100, David Woodhouse wrote:
> This is v7 of the series to clean up the KVM clock, rebased onto
> kvm-x86/next (patch 1 of v6 is already merged there as commit
> 710b3a30f407).
>
> The KVM clock has historically suffered from three problems:
>
> 1. Imprecision: get_kvmclock_ns() computed the clock from the *host*
> TSC without applying guest TSC scaling, causing systemic drift from
> the values the guest computes from its own TSC.
>
> [...]
Applied two more Xen patches to kvm-x86 clocks.
Given that KVM was updating the wrong sub-leaf (which amused me greatly), I
didn't see any point in waiting for the new uAPI updates to yank out the CPUID
updates. Holler if you feel strongly that that change in particular should be
bundled with the kernel that adds the TSC scaling uAPI, omitting these changes
from 7.3 and waiting for 7.4 is trivial. I'm just trying to reduce the number
of in-flight patches we need to keep track of.
Thanks!
[20/36] KVM: x86/xen: Prevent runstate times from becoming negative
https://github.com/kvm-x86/linux/commit/36a85200643e
...
[22/36] KVM: x86: Remove runtime Xen TSC frequency CPUID update
https://github.com/kvm-x86/linux/commit/7d3bd21e457b
--
https://github.com/kvm-x86/linux/tree/next
