The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	 Shuah Khan <skhan@linuxfoundation.org>,
	Thomas Gleixner <tglx@kernel.org>,
	 Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org,  "H. Peter Anvin" <hpa@zytor.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Juergen Gross <jgross@suse.com>,
	 Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Paul Durrant <paul@xen.org>,  Jonathan Cameron <jic23@kernel.org>,
	Sascha Bischoff <Sascha.Bischoff@arm.com>,
	 Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
	Jack Allister <jalliste@amazon.com>,
	 Dongli Zhang <dongli.zhang@oracle.com>,
	joe.jin@oracle.com, kvm@vger.kernel.org,
	 linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 xen-devel@lists.xenproject.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 15/36] KVM: x86: Fix compute_guest_tsc() to handle negative time deltas
Date: Mon, 27 Jul 2026 17:51:59 -0700	[thread overview]
Message-ID: <amf9L65ZlPOqJm7A@google.com> (raw)
In-Reply-To: <b38f67187d3312c4bf2c9eddf89e14e8b10573d6.camel@infradead.org>

On Sat, Jul 25, 2026, David Woodhouse wrote:
> On Fri, 2026-07-24 at 14:27 -0700, Sean Christopherson wrote:
> > On Fri, Jul 03, 2026, David Woodhouse wrote:
> > > From: David Woodhouse <dwmw@amazon.co.uk>
> > > 
> > > The compute_guest_tsc() function computes the guest TSC at a given
> > > kernel_ns timestamp. When the master clock reference point
> > > (master_kernel_ns) is earlier than vcpu->arch.this_tsc_nsec, the delta
> > > is negative. Since pvclock_scale_delta() takes a u64, the negative
> > > value wraps to a huge positive number, producing a wildly wrong result.
> > > 
> > > Handle negative deltas explicitly by negating the delta, scaling it,
> > > and subtracting from this_tsc_write.
> > 
> > Does this need 
> > 
> >   Cc: stable@vger.kernel.org
> > 
> > or is this a "technically a bug fix, but can't happen in practice" sort of thing?
> 
> Honestly, there's so much hosed in kvmclock that we could debate a
> cc:stable for half of this series. I'm not doing *any* of this to
> actually add new features. For this one I'm not sure it's reachable in
> practice; I think I did it mostly to shut Sashiko up.

Heh, in that case, throw a blurb in the changelog stating as much.  Knowing that
a bug is likely unreachable in practice is helpful, e.g. in the super unlikely
case that this change breaks someone.

> I think even in the KVM_SET_CLOCK_GUEST it can't trigger, although I
> have fantasies about changing the way KVM_SET_CLOCK_GUEST works to fix
> that final ±1ns imprecision (which requires separate work on the
> timekeeping core), that *might* trigger the negative delta here...



  reply	other threads:[~2026-07-28  0:52 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 21:17 [PATCH v6 00/36] Cleaning up the KVM clock mess David Woodhouse
2026-07-03 21:17 ` [PATCH v6 01/36] KVM: x86/xen: Do not corrupt KVM clock in kvm_xen_shared_info_init() David Woodhouse
2026-07-03 21:17 ` [PATCH v6 02/36] KVM: x86: Improve accuracy of KVM clock when TSC scaling is in force David Woodhouse
2026-07-24 21:10   ` Sean Christopherson
2026-07-03 21:17 ` [PATCH v6 03/36] UAPI: x86: Move pvclock-abi to UAPI for x86 platforms David Woodhouse
2026-07-03 21:17 ` [PATCH v6 04/36] KVM: selftests: Use UAPI pvclock-abi.h in xen_shinfo_test David Woodhouse
2026-07-03 21:17 ` [PATCH v6 05/36] KVM: x86: Add KVM_[GS]ET_CLOCK_GUEST for accurate KVM clock migration David Woodhouse
2026-07-24 21:17   ` Sean Christopherson
2026-07-25  7:47     ` David Woodhouse
2026-07-28  1:15       ` Sean Christopherson
2026-07-28  2:13         ` David Woodhouse
2026-07-03 21:17 ` [PATCH v6 06/36] KVM: selftests: Add KVM/PV clock selftest to prove timer correction David Woodhouse
2026-07-03 21:17 ` [PATCH v6 07/36] KVM: x86: Explicitly disable TSC scaling without CONSTANT_TSC David Woodhouse
2026-07-03 21:17 ` [PATCH v6 08/36] KVM: x86: Activate master clock immediately on vCPU creation David Woodhouse
2026-07-24 21:19   ` Sean Christopherson
2026-07-25  7:59     ` David Woodhouse
2026-07-25 12:45       ` David Woodhouse
2026-07-03 21:17 ` [PATCH v6 09/36] KVM: x86: Add KVM_VCPU_TSC_SCALE and fix the documentation on TSC migration David Woodhouse
2026-07-03 21:17 ` [PATCH v6 10/36] KVM: x86: Avoid NTP frequency skew for KVM clock on 32-bit host David Woodhouse
2026-07-03 21:17 ` [PATCH v6 11/36] KVM: x86: Fold __get_kvmclock() into get_kvmclock() David Woodhouse
2026-07-03 21:17 ` [PATCH v6 12/36] KVM: x86: Restructure get_kvmclock() David Woodhouse
2026-07-24 21:29   ` Sean Christopherson
2026-07-25  7:53     ` David Woodhouse
2026-07-28  0:49       ` Sean Christopherson
2026-07-03 21:17 ` [PATCH v6 13/36] KVM: x86: Fix KVM clock precision in get_kvmclock() with TSC scaling David Woodhouse
2026-07-03 21:17 ` [PATCH v6 14/36] KVM: x86: Use get_kvmclock() in kvm_get_wall_clock_epoch() David Woodhouse
2026-07-03 21:17 ` [PATCH v6 15/36] KVM: x86: Fix compute_guest_tsc() to handle negative time deltas David Woodhouse
2026-07-24 21:27   ` Sean Christopherson
2026-07-25  7:56     ` David Woodhouse
2026-07-28  0:51       ` Sean Christopherson [this message]
2026-07-25 17:11     ` David Woodhouse
2026-07-03 21:17 ` [PATCH v6 16/36] KVM: x86: Restructure kvm_guest_time_update() for TSC upscaling David Woodhouse
2026-07-03 21:17 ` [PATCH v6 17/36] KVM: x86: Simplify and comment kvm_get_time_scale() David Woodhouse
2026-07-03 21:17 ` [PATCH v6 18/36] KVM: x86: Remove implicit rdtsc() from kvm_compute_l1_tsc_offset() David Woodhouse
2026-07-03 21:17 ` [PATCH v6 19/36] KVM: x86: Improve synchronization in kvm_synchronize_tsc() David Woodhouse
2026-07-03 21:17 ` [PATCH v6 20/36] KVM: x86: Kill last_tsc_{nsec,write,offset} fields David Woodhouse
2026-07-03 21:18 ` [PATCH v6 21/36] KVM: x86: Replace nr_vcpus_matched_tsc count with all_vcpus_matched_tsc bool David Woodhouse
2026-07-03 21:18 ` [PATCH v6 22/36] KVM: x86: Allow KVM master clock mode when TSCs are offset from each other David Woodhouse
2026-07-03 21:18 ` [PATCH v6 23/36] KVM: selftests: Add master clock offset test David Woodhouse
2026-07-03 21:18 ` [PATCH v6 24/36] KVM: x86: Factor out kvm_use_master_clock() David Woodhouse
2026-07-03 21:18 ` [PATCH v6 25/36] KVM: x86: Avoid gratuitous global clock updates David Woodhouse
2026-07-03 21:18 ` [PATCH v6 26/36] KVM: x86/xen: Prevent runstate times from becoming negative David Woodhouse
2026-07-03 21:18 ` [PATCH v6 27/36] KVM: x86: Avoid redundant masterclock updates from multiple vCPUs David Woodhouse
2026-07-03 21:18 ` [PATCH v6 28/36] KVM: x86: Remove runtime Xen TSC frequency CPUID update David Woodhouse
2026-07-03 21:18 ` [PATCH v6 29/36] KVM: selftests: Add Xen/generic CPUID timing leaf test David Woodhouse
2026-07-03 21:18 ` [PATCH v6 30/36] KVM: x86: Re-synchronize TSC after KVM_SET_TSC_KHZ David Woodhouse
2026-07-03 21:18 ` [PATCH v6 31/36] KVM: selftests: Add Xen runstate migration test David Woodhouse
2026-07-26  9:21   ` David Woodhouse
2026-07-03 21:18 ` [PATCH v6 32/36] KVM: x86: Use ktime_get_snapshot_id() for master clock David Woodhouse
2026-07-03 21:18 ` [PATCH v6 33/36] KVM: x86: Compute kvmclock base without pvclock_gtod_data David Woodhouse
2026-07-03 21:18 ` [PATCH v6 34/36] KVM: x86: Cache host vclock_mode for masterclock eligibility checks David Woodhouse
2026-07-03 21:18 ` [PATCH v6 35/36] KVM: x86: Remove pvclock_gtod_data and private timekeeping code David Woodhouse
2026-07-03 21:18 ` [PATCH v6 36/36] KVM: x86: Activate master clock from kvm_arch_init_vm() David Woodhouse

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=amf9L65ZlPOqJm7A@google.com \
    --to=seanjc@google.com \
    --cc=Sascha.Bischoff@arm.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=dongli.zhang@oracle.com \
    --cc=dwmw2@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jalliste@amazon.com \
    --cc=jgross@suse.com \
    --cc=jic23@kernel.org \
    --cc=joe.jin@oracle.com \
    --cc=joey.gouly@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@kernel.org \
    --cc=vkuznets@redhat.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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