From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Durrant <paul@xen.org>, David Woodhouse <dwmw@amazon.co.uk>,
Dongli Zhang <dongli.zhang@oracle.com>
Subject: Re: [PATCH v9 02/21] KVM: x86: Improve accuracy of KVM clock when TSC scaling is in force
Date: Wed, 12 Aug 2026 13:08:44 -0700 [thread overview]
Message-ID: <anzSzC488HgK76Eu@google.com> (raw)
In-Reply-To: <20260810225500.869288-3-seanjc@google.com>
On Mon, Aug 10, 2026, Sean Christopherson wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
>
> The kvm_guest_time_update() function scales the host TSC frequency to
> the guest's using kvm_scale_tsc() and the v->arch.l1_tsc_scaling_ratio
> scaling ratio previously calculated for that vCPU. Then calculates the
> scaling factors for the KVM clock itself based on that guest TSC
> frequency.
>
> However, it uses kHz as the unit when scaling, and then multiplies by
> 1000 only at the end.
>
> With a host TSC frequency of 3000MHz and a guest set to 2500MHz, the
> result of kvm_scale_tsc() will actually come out at 2,499,999kHz. So
> the KVM clock advertised to the guest is based on a frequency of
> 2,499,999,000 Hz.
>
> By using Hz as the unit from the beginning, the KVM clock would be based
> on a more accurate frequency of 2,499,999,999 Hz in this example.
>
> Use u64 for the hw_tsc_hz field since an unsigned int would overflow for
> TSC frequencies above 4GHz. Use div_u64() for the Xen CPUID leaf to
> play nice with 32-bit kernels.
>
> Fixes: 78db6a503796 ("KVM: x86: rewrite handling of scaled TSC for kvmclock")
> Reviewed-by: Paul Durrant <paul@xen.org>
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> Tested-by: Dongli Zhang <dongli.zhang@oracle.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/include/asm/kvm_host.h | 2 +-
> arch/x86/kvm/cpuid.c | 1 +
> arch/x86/kvm/x86.c | 18 ++++++++++--------
> 3 files changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
> index 283847619ff8..6ddc988576d0 100644
> --- a/arch/x86/include/asm/kvm_host.h
> +++ b/arch/x86/include/asm/kvm_host.h
> @@ -864,7 +864,7 @@ struct kvm_vcpu_arch {
> gpa_t time;
> s8 pvclock_tsc_shift;
> u32 pvclock_tsc_mul;
> - unsigned int hw_tsc_khz;
> + u64 hw_tsc_hz;
From https://sashiko.dev/#/patchset/20260810225500.869288-1-seanjc%40google.com:
: > diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
: > index b517257a63153..099c3da20547d 100644
: > --- a/arch/x86/include/asm/kvm_host.h
: > +++ b/arch/x86/include/asm/kvm_host.h
: > @@ -1004,7 +1004,7 @@ struct kvm_vcpu_arch {
: > gpa_t time;
: > s8 pvclock_tsc_shift;
: > u32 pvclock_tsc_mul;
: > - unsigned int hw_tsc_khz;
: > + u64 hw_tsc_hz;
: > struct gfn_to_pfn_cache pv_time;
: > /* set guest stopped flag in pvclock flags field */
: > bool pvclock_set_guest_stopped_request;
:
: The commit message mentions using div_u64() for the Xen CPUID leaf, but is
: the actual update to kvm_cpuid() missing here?
:
: It appears kvm_cpuid() still references the old field name:
:
: arch/x86/kvm/cpuid.c:kvm_cpuid() {
: ...
: *eax = vcpu->arch.hw_tsc_khz;
: ...
: }
:
: Since the field was renamed to hw_tsc_hz in struct kvm_vcpu_arch, will this
: cause a build failure when compiling for x86?
The changelog is stale. This will be applied on top of commit 7d3bd21e457b
("KVM: x86: Remove runtime Xen TSC frequency CPUID update") that's sitting in
kvm-x86/clocks. I'll drop the stale sentence from the changelog when applying.
next prev parent reply other threads:[~2026-08-12 20:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 22:54 [PATCH v9 00/21] KVM: x86: Cleaning up the KVM clock mess, part 1 Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 01/21] KVM: x86: Update "last guest TSC" snapshot prior to enabling IRQs/preemption Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 02/21] KVM: x86: Improve accuracy of KVM clock when TSC scaling is in force Sean Christopherson
2026-08-12 20:08 ` Sean Christopherson [this message]
2026-08-10 22:54 ` [PATCH v9 03/21] KVM: x86: Explicitly disable TSC scaling without CONSTANT_TSC Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 04/21] KVM: x86: Activate master clock immediately on vCPU creation Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 05/21] KVM: x86: Compute kvmclock base without pvclock_gtod_data Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 06/21] KVM: x86: Avoid NTP frequency skew for KVM clock on 32-bit host Sean Christopherson
2026-08-12 20:45 ` Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 07/21] KVM: x86: Drop unnecessary CPU pinning when computing/getting kvmclock Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 08/21] KVM: x86: Move "no master clock" fallback from __get_kvmclock() to get_kvmclock() Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 09/21] KVM: x86: Wrap all of __get_kvmclock_master_clock() with CONFIG_X86_64=y Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 10/21] KVM: x86: Fall back to non-master-clock if clockread fails in get_kvmclock() Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 11/21] KVM: x86: Fix KVM clock precision in get_kvmclock() with TSC scaling Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 12/21] KVM: x86: Use get_kvmclock() in kvm_get_wall_clock_epoch() Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 13/21] KVM: x86: Fix compute_guest_tsc() to handle negative time deltas Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 14/21] KVM: x86: Disable preemption, not IRQs, when getting TSC+freq pair Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 15/21] KVM: x86: Make master clock logic in guest PV clock updates 64-bit only Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 16/21] KVM: x86: Upscale TSC to "now", not master clock when updating PV clocks Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 17/21] KVM: x86: Simplify and comment kvm_get_time_scale() Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 18/21] KVM: x86: Remove implicit rdtsc() from kvm_compute_l1_tsc_offset() Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 19/21] KVM: x86: Use kernel timekeeping snapshots for getting kvmclock time since boot Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 20/21] KVM: x86: Use kernel timekeeping snapshot for monotonic clock Sean Christopherson
2026-08-10 22:54 ` [PATCH v9 21/21] KVM: x86: Use kernel timekeeping snapshot to get walltime+TSC Sean Christopherson
2026-08-11 13:58 ` [PATCH v9 00/21] KVM: x86: Cleaning up the KVM clock mess, part 1 Woodhouse, David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=anzSzC488HgK76Eu@google.com \
--to=seanjc@google.com \
--cc=dongli.zhang@oracle.com \
--cc=dwmw@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox