From: Paolo Bonzini <pbonzini@redhat.com>
Date: Wed, 19 Mar 2025 13:11:59 +0000 (-0400)
Subject: Merge tag 'kvm-x86-pvclock-6.15' of https://github.com/kvm-x86/linux into HEAD
X-Git-Tag: v6.15-rc1~195^2~5
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=fcce7c1e7d39bc35651ad0fbdeaa15276ea7fb15;p=thirdparty%2Fkernel%2Flinux.git

Merge tag 'kvm-x86-pvclock-6.15' of https://github.com/kvm-x86/linux into HEAD

KVM PV clock changes for 6.15:

 - Don't take kvm->lock when iterating over vCPUs in the suspend notifier to
   fix a largely theoretical deadlock.

 - Use the vCPU's actual Xen PV clock information when starting the Xen timer,
   as the cached state in arch.hv_clock can be stale/bogus.

 - Fix a bug where KVM could bleed PVCLOCK_GUEST_STOPPED across different
   PV clocks.

 - Restrict PVCLOCK_GUEST_STOPPED to kvmclock, as KVM's suspend notifier only
   accounts for kvmclock, and there's no evidence that the flag is actually
   supported by Xen guests.

 - Clean up the per-vCPU "cache" of its reference pvclock, and instead only
   track the vCPU's TSC scaling (multipler+shift) metadata (which is moderately
   expensive to compute, and rarely changes for modern setups).
---

fcce7c1e7d39bc35651ad0fbdeaa15276ea7fb15