]> www.infradead.org Git - users/dwmw2/linux.git/commit
KVM: x86: Kill KVM_REQ_GLOBAL_CLOCK_UPDATE clocks-killsync
authorDavid Woodhouse <dwmw@amazon.co.uk>
Thu, 18 Apr 2024 11:31:54 +0000 (12:31 +0100)
committerDavid Woodhouse <dwmw@amazon.co.uk>
Fri, 26 Apr 2024 14:20:36 +0000 (15:20 +0100)
commit0b97c08cdb726f6d86449d5f4417d75720e93222
treeb527afdaf3efe59b81e1456436ebc34b4ffcdcbf
parent42c7040e8ab2c167ef33b300eaccf2eec54af25d
KVM: x86: Kill KVM_REQ_GLOBAL_CLOCK_UPDATE

This was introduced in commit 0061d53daf26 ("KVM: x86: limit difference
between kvmclock updates") to reduce cross-vCPU differences which arose
because the KVM clock was based on CLOCK_MONOTONIC and thus subject to
NTP frequency corrections.

However, commit 53fafdbb8b21 ("KVM: x86: switch KVMCLOCK base to
monotonic raw clock") switched to using CLOCK_MONOTONIC_RAW as the basis
for the KVM clock, avoiding the NTP frequency skew altogether.

So remove KVM_REQ_GLOBAL_CLOCK_UPDATE. In kvm_write_system_time(), all
that's needed is a single KVM_REQ_CLOCK_UPDATE for the vCPU whose KVM
clock is being configured.

Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
Reviewed-by: Paul Durrant <paul@xen.org>
arch/x86/include/asm/kvm_host.h
arch/x86/kvm/x86.c