[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH v11 02/23] KVM: x86: Kill last_tsc_{nsec,write,offset} fields



From: David Woodhouse <dwmw@xxxxxxxxxxxx>

These pointlessly duplicate the cur_tsc_{nsec,write,offset} values.
The only place they were used was where the TSC is stable and a new
vCPU is being synchronized to the previous setting, in which case the
cur_tsc_* value is definitely identical.

Rename last_tsc_khz and last_tsc_scaling_ratio to cur_tsc_khz and
cur_tsc_scaling_ratio respectively, since they are properties of the
current TSC generation.

Since cur_tsc_offset now serves as the single source of truth for the
TSC generation's offset, the backwards-TSC adjustment (used during S4
resume when the host TSC resets) must also update cur_tsc_offset by
the same delta applied to all vCPUs (scaled to the guest TSC rate, as
adjust_tsc_offset_host() does). Without this, subsequent vCPUs that
synchronize after the adjustment would get the stale pre-S4 offset.

Since a synchronization now establishes an absolute offset which (via
a matched reuse of cur_tsc_offset) already includes any backwards-TSC
delta, clear the vCPU's pending tsc_offset_adjustment when writing it:
the deferred per-vCPU compensation would otherwise be applied on top
at the next vcpu_load, doubling the delta. Previously this could not
happen, because zeroing the last_tsc values disabled offset matching
entirely after a backwards TSC.

Signed-off-by: David Woodhouse <dwmw@xxxxxxxxxxxx>
Reviewed-by: Paul Durrant <paul@xxxxxxx>
---
 Documentation/virt/kvm/locking.rst |  2 +-
 arch/x86/include/asm/kvm_host.h    |  7 +--
 arch/x86/kvm/x86.c                 | 72 ++++++++++++++++++------------
 3 files changed, 47 insertions(+), 34 deletions(-)

diff --git a/Documentation/virt/kvm/locking.rst 
b/Documentation/virt/kvm/locking.rst
index 662231e958a0..4548b61a7652 100644
--- a/Documentation/virt/kvm/locking.rst
+++ b/Documentation/virt/kvm/locking.rst
@@ -263,7 +263,7 @@ time it will be set using the Dirty tracking mechanism 
described above.
 
 :Type:         raw_spinlock_t
 :Arch:         x86
-:Protects:     - kvm_arch::{last_tsc_write,last_tsc_nsec,last_tsc_offset}
+:Protects:     - kvm_arch::{cur_tsc_write,cur_tsc_nsec,cur_tsc_offset}
                - tsc offset in vmcb
 :Comment:      'raw' because updating the tsc offsets must not be preempted.
 
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index e2eef7057bd3..ea48b1949316 100644
--- a/arch/x86/include/asm/kvm_host.h
+++ b/arch/x86/include/asm/kvm_host.h
@@ -1236,11 +1236,8 @@ struct kvm_arch {
         * preemption-disabled region, so it must be a raw spinlock.
         */
        raw_spinlock_t tsc_write_lock;
-       u64 last_tsc_nsec;
-       u64 last_tsc_write;
-       u32 last_tsc_khz;
-       u64 last_tsc_offset;
-       u64 last_tsc_scaling_ratio;
+       u32 cur_tsc_khz;
+       u64 cur_tsc_scaling_ratio;
        u64 cur_tsc_nsec;
        u64 cur_tsc_write;
        u64 cur_tsc_offset;
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 7a2b0b99373f..90f9b07ef749 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -1334,17 +1334,24 @@ static void __kvm_synchronize_tsc(struct kvm_vcpu 
*vcpu, u64 offset, u64 tsc,
                vcpu->kvm->arch.user_set_tsc = true;
 
        /*
-        * We also track th most recent recorded KHZ, write and time to
-        * allow the matching interval to be extended at each write.
+        * Track the TSC frequency, scaling ratio, and offset for the current
+        * generation. These are used to detect matching TSC writes and to
+        * compute the guest TSC from the host clock.
         */
-       kvm->arch.last_tsc_nsec = ns;
-       kvm->arch.last_tsc_write = tsc;
-       kvm->arch.last_tsc_khz = vcpu->arch.virtual_tsc_khz;
-       kvm->arch.last_tsc_offset = offset;
-       kvm->arch.last_tsc_scaling_ratio = vcpu->arch.l1_tsc_scaling_ratio;
+       kvm->arch.cur_tsc_khz = vcpu->arch.virtual_tsc_khz;
+       kvm->arch.cur_tsc_scaling_ratio = vcpu->arch.l1_tsc_scaling_ratio;
 
        vcpu->arch.last_guest_tsc = tsc;
 
+       /*
+        * The offset written below is absolute, superseding any backwards-TSC
+        * compensation still pending from kvm_arch_enable_virtualization_cpu()
+        * (which has already been folded into cur_tsc_offset, and thus into
+        * a matched @offset); applying it again at the next vcpu_load would
+        * double it.
+        */
+       vcpu->arch.tsc_offset_adjustment = 0;
+
        kvm_vcpu_write_tsc_offset(vcpu, offset);
 
        if (!matched) {
@@ -1354,8 +1361,6 @@ static void __kvm_synchronize_tsc(struct kvm_vcpu *vcpu, 
u64 offset, u64 tsc,
                 * nanosecond time, offset, and write, so if TSCs are in
                 * sync, we can match exact offset, and if not, we can match
                 * exact software computation in compute_guest_tsc()
-                *
-                * These values are tracked in kvm->arch.cur_xxx variables.
                 */
                kvm->arch.cur_tsc_generation++;
                kvm->arch.cur_tsc_nsec = ns;
@@ -1395,7 +1400,7 @@ void kvm_synchronize_tsc(struct kvm_vcpu *vcpu, u64 
*user_value)
        }
 
        offset = kvm_compute_l1_tsc_offset(vcpu, host_tsc, data);
-       elapsed = ns - kvm->arch.last_tsc_nsec;
+       elapsed = ns - kvm->arch.cur_tsc_nsec;
 
        if (vcpu->arch.virtual_tsc_khz) {
                if (data == 0) {
@@ -1405,7 +1410,7 @@ void kvm_synchronize_tsc(struct kvm_vcpu *vcpu, u64 
*user_value)
                         */
                        synchronizing = true;
                } else if (kvm->arch.user_set_tsc) {
-                       u64 tsc_exp = kvm->arch.last_tsc_write +
+                       u64 tsc_exp = kvm->arch.cur_tsc_write +
                                                nsec_to_cycles(vcpu, elapsed);
                        u64 tsc_hz = vcpu->arch.virtual_tsc_khz * 1000LL;
                        /*
@@ -1436,15 +1441,12 @@ void kvm_synchronize_tsc(struct kvm_vcpu *vcpu, u64 
*user_value)
         * it's better to try to match offsets from the beginning.
          */
        if (synchronizing &&
-           vcpu->arch.virtual_tsc_khz == kvm->arch.last_tsc_khz) {
+           vcpu->arch.virtual_tsc_khz == kvm->arch.cur_tsc_khz) {
                /*
                 * If synchronizing, advance the reference point to "now"
                 * so the matching window slides forward with each vCPU.
-                * Extrapolate from the generation's own origin: 'elapsed'
-                * is measured from the most recent write, which lies on
-                * the generation's line only for the first matched write.
                 */
-               u64 delta = nsec_to_cycles(vcpu, ns - kvm->arch.cur_tsc_nsec);
+               u64 delta = nsec_to_cycles(vcpu, elapsed);
 
                data = kvm->arch.cur_tsc_write + delta;
 
@@ -1615,7 +1617,7 @@ static void pvclock_update_vm_gtod_copy(struct kvm *kvm)
                 * get_kvmclock() to compute kvmclock from the host TSC
                 * without needing a vCPU reference.
                 */
-               ka->master_tsc_scaling_ratio = ka->last_tsc_scaling_ratio;
+               ka->master_tsc_scaling_ratio = ka->cur_tsc_scaling_ratio;
                tsc_hz = (u64)get_cpu_tsc_khz() * HZ_PER_KHZ;
                if (tsc_hz && kvm_caps.has_tsc_control)
                        tsc_hz = kvm_scale_tsc(tsc_hz,
@@ -3344,8 +3346,8 @@ static int kvm_arch_tsc_set_attr(struct kvm_vcpu *vcpu,
                raw_spin_lock_irqsave(&kvm->arch.tsc_write_lock, flags);
 
                matched = (vcpu->arch.virtual_tsc_khz &&
-                          kvm->arch.last_tsc_khz == vcpu->arch.virtual_tsc_khz 
&&
-                          kvm->arch.last_tsc_offset == offset);
+                          kvm->arch.cur_tsc_khz == vcpu->arch.virtual_tsc_khz 
&&
+                          kvm->arch.cur_tsc_offset == offset);
 
                tsc = kvm_scale_tsc(rdtsc(), vcpu->arch.l1_tsc_scaling_ratio) + 
offset;
                ns = get_kvmclock_base_ns();
@@ -9803,7 +9805,7 @@ int kvm_arch_enable_virtualization_cpu(void)
 {
        struct kvm *kvm;
        struct kvm_vcpu *vcpu;
-       unsigned long i;
+       unsigned long i, flags;
        int ret;
        u64 local_tsc;
        u64 max_tsc = 0;
@@ -9874,6 +9876,24 @@ int kvm_arch_enable_virtualization_cpu(void)
        if (backwards_tsc) {
                u64 delta_cyc = max_tsc - local_tsc;
                list_for_each_entry(kvm, &vm_list, vm_list) {
+                       /*
+                        * Hold tsc_write_lock across the per-vCPU adjustments
+                        * AND the generation reference offset adjustment, so
+                        * that a concurrent TSC synchronization cannot observe
+                        * one without the other (it would compute an offset
+                        * with the delta applied twice, or not at all).
+                        *
+                        * The generation's reference offset is adjusted by the
+                        * same (guest-scaled, as adjust_tsc_offset_host()
+                        * does for each vCPU) delta, so that future
+                        * KVM_SET_TSC / vCPU creation still matches against
+                        * the adjusted TSC timeline. The recorded
+                        * {cur_tsc_nsec, cur_tsc_write} pair needs no
+                        * adjustment: the guest TSC is kept continuous
+                        * across the host TSC jump, and that pair lives in
+                        * the wall-clock/guest-cycle domain.
+                        */
+                       raw_spin_lock_irqsave(&kvm->arch.tsc_write_lock, flags);
                        kvm->arch.backwards_tsc_observed = true;
                        kvm_for_each_vcpu(i, vcpu, kvm) {
                                vcpu->arch.tsc_offset_adjustment += delta_cyc;
@@ -9881,14 +9901,10 @@ int kvm_arch_enable_virtualization_cpu(void)
                                kvm_make_request(KVM_REQ_MASTERCLOCK_UPDATE, 
vcpu);
                        }
 
-                       /*
-                        * We have to disable TSC offset matching.. if you were
-                        * booting a VM while issuing an S4 host suspend....
-                        * you may have some problem.  Solving this issue is
-                        * left as an exercise to the reader.
-                        */
-                       kvm->arch.last_tsc_nsec = 0;
-                       kvm->arch.last_tsc_write = 0;
+                       kvm->arch.cur_tsc_offset +=
+                               kvm_scale_tsc(delta_cyc,
+                                             kvm->arch.cur_tsc_scaling_ratio);
+                       raw_spin_unlock_irqrestore(&kvm->arch.tsc_write_lock, 
flags);
                }
 
        }
-- 
2.43.0




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.