From: Zachary Amsden <zamsden@redhat.com>
To: KVM <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Glauber Costa <glommer@redhat.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
Zachary Amsden <zamsden@redhat.com>, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Glauber Costa <glommer@redhat.com>
Subject: [PATCH 14/18] Fix a possible backwards warp of kvmclock
Date: Mon, 12 Jul 2010 16:25:34 -1000 [thread overview]
Message-ID: <1278987938-23873-15-git-send-email-zamsden@redhat.com> (raw)
In-Reply-To: <1278987938-23873-1-git-send-email-zamsden@redhat.com>
Kernel time, which advances in discrete steps may progress much slower
than TSC. As a result, when kvmclock is adjusted to a new base, the
apparent time to the guest, which runs at a much higher, nsec scaled
rate based on the current TSC, may have already been observed to have
a larger value (kernel_ns + scaled tsc) than the value to which we are
setting it (kernel_ns + 0).
We must instead compute the clock as potentially observed by the guest
for kernel_ns to make sure it does not go backwards.
Signed-off-by: Zachary Amsden <zamsden@redhat.com>
---
arch/x86/include/asm/kvm_host.h | 2 +
arch/x86/kvm/x86.c | 43 +++++++++++++++++++++++++++++++++++++-
2 files changed, 43 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index d9e0aa0..94dd16b 100644
--- a/arch/x86/include/asm/kvm_host.h
+++ b/arch/x86/include/asm/kvm_host.h
@@ -340,6 +340,8 @@ struct kvm_vcpu_arch {
struct page *time_page;
u64 last_host_tsc;
u64 last_host_ns;
+ u64 last_guest_tsc;
+ u64 last_kernel_ns;
bool nmi_pending;
bool nmi_injected;
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 08bd15b..f9994c3 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -974,14 +974,15 @@ static int kvm_write_guest_time(struct kvm_vcpu *v)
struct kvm_vcpu_arch *vcpu = &v->arch;
void *shared_kaddr;
unsigned long this_tsc_khz;
- s64 kernel_ns;
+ s64 kernel_ns, max_kernel_ns;
+ u64 tsc_timestamp;
if ((!vcpu->time_page))
return 0;
/* Keep irq disabled to prevent changes to the clock */
local_irq_save(flags);
- kvm_get_msr(v, MSR_IA32_TSC, &vcpu->hv_clock.tsc_timestamp);
+ kvm_get_msr(v, MSR_IA32_TSC, &tsc_timestamp);
kernel_ns = get_kernel_ns();
this_tsc_khz = __get_cpu_var(cpu_tsc_khz);
local_irq_restore(flags);
@@ -991,13 +992,49 @@ static int kvm_write_guest_time(struct kvm_vcpu *v)
return 1;
}
+ /*
+ * Time as measured by the TSC may go backwards when resetting the base
+ * tsc_timestamp. The reason for this is that the TSC resolution is
+ * higher than the resolution of the other clock scales. Thus, many
+ * possible measurments of the TSC correspond to one measurement of any
+ * other clock, and so a spread of values is possible. This is not a
+ * problem for the computation of the nanosecond clock; with TSC rates
+ * around 1GHZ, there can only be a few cycles which correspond to one
+ * nanosecond value, and any path through this code will inevitably
+ * take longer than that. However, with the kernel_ns value itself,
+ * the precision may be much lower, down to HZ granularity. If the
+ * first sampling of TSC against kernel_ns ends in the low part of the
+ * range, and the second in the high end of the range, we can get:
+ *
+ * (TSC - offset_low) * S + kns_old > (TSC - offset_high) * S + kns_new
+ *
+ * As the sampling errors potentially range in the thousands of cycles,
+ * it is possible such a time value has already been observed by the
+ * guest. To protect against this, we must compute the system time as
+ * observed by the guest and ensure the new system time is greater.
+ */
+ max_kernel_ns = 0;
+ if (vcpu->hv_clock.tsc_timestamp && vcpu->last_guest_tsc) {
+ max_kernel_ns = vcpu->last_guest_tsc -
+ vcpu->hv_clock.tsc_timestamp;
+ max_kernel_ns = pvclock_scale_delta(max_kernel_ns,
+ vcpu->hv_clock.tsc_to_system_mul,
+ vcpu->hv_clock.tsc_shift);
+ max_kernel_ns += vcpu->last_kernel_ns;
+ }
+
if (unlikely(vcpu->hw_tsc_khz != this_tsc_khz)) {
kvm_set_time_scale(this_tsc_khz, &vcpu->hv_clock);
vcpu->hw_tsc_khz = this_tsc_khz;
}
+ if (max_kernel_ns > kernel_ns)
+ kernel_ns = max_kernel_ns;
+
/* With all the info we got, fill in the values */
+ vcpu->hv_clock.tsc_timestamp = tsc_timestamp;
vcpu->hv_clock.system_time = kernel_ns + v->kvm->arch.kvmclock_offset;
+ vcpu->last_kernel_ns = kernel_ns;
vcpu->hv_clock.flags = 0;
/*
@@ -4918,6 +4955,8 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
if (hw_breakpoint_active())
hw_breakpoint_restore();
+ kvm_get_msr(vcpu, MSR_IA32_TSC, &vcpu->arch.last_guest_tsc);
+
atomic_set(&vcpu->guest_mode, 0);
smp_wmb();
local_irq_enable();
--
1.7.1
next prev parent reply other threads:[~2010-07-13 2:27 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 2:25 KVM timekeeping fixes, V2 Zachary Amsden
2010-07-13 2:25 ` [PATCH 01/18] Make TSC offset writes non-preemptible Zachary Amsden
2010-07-13 21:33 ` Rik van Riel
2010-07-18 14:28 ` Avi Kivity
2010-07-18 14:30 ` Avi Kivity
2010-07-13 2:25 ` [PATCH 02/18] Fix SVM VMCB reset Zachary Amsden
2010-07-13 21:37 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 03/18] TSC reset compensation Zachary Amsden
2010-07-13 22:11 ` Rik van Riel
2010-07-18 14:34 ` Avi Kivity
2010-07-19 20:01 ` Zachary Amsden
2010-07-13 2:25 ` [PATCH 04/18] Make cpu_tsc_khz updates use local CPU Zachary Amsden
2010-07-14 14:41 ` Rik van Riel
2010-07-18 14:45 ` Avi Kivity
2010-07-19 20:06 ` Zachary Amsden
2010-07-20 8:53 ` Avi Kivity
2010-07-20 21:57 ` Zachary Amsden
2010-07-13 2:25 ` [PATCH 05/18] Warn about unstable TSC Zachary Amsden
2010-07-14 15:02 ` Rik van Riel
2010-07-18 14:47 ` Avi Kivity
2010-07-13 2:25 ` [PATCH 06/18] Unify TSC logic Zachary Amsden
2010-07-14 15:53 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 07/18] Fix deep C-state TSC desynchronization Zachary Amsden
2010-07-14 16:14 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 08/18] Add helper functions for time computation Zachary Amsden
2010-07-14 19:02 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 09/18] Robust TSC compensation Zachary Amsden
2010-07-13 20:34 ` Marcelo Tosatti
2010-07-13 21:15 ` Zachary Amsden
2010-07-13 21:42 ` David S. Ahern
2010-07-13 21:45 ` Zachary Amsden
2010-07-13 23:32 ` Zachary Amsden
2010-07-14 22:33 ` Rik van Riel
2010-07-18 14:52 ` Avi Kivity
2010-07-19 20:39 ` Zachary Amsden
2010-07-13 2:25 ` [PATCH 10/18] Keep SMP VMs more in sync on unstable TSC Zachary Amsden
2010-07-15 2:13 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 11/18] Perform hardware_enable in CPU_STARTING callback Zachary Amsden
2010-07-15 2:15 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 12/18] Add clock sync request to hardware enable Zachary Amsden
2010-07-15 2:32 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 13/18] Move scale_delta into common header Zachary Amsden
2010-07-15 2:35 ` Rik van Riel
2010-07-13 2:25 ` Zachary Amsden [this message]
2010-07-15 2:37 ` [PATCH 14/18] Fix a possible backwards warp of kvmclock Rik van Riel
2010-07-13 2:25 ` [PATCH 15/18] Implement getnsboottime kernel API Zachary Amsden
2010-07-15 2:41 ` Rik van Riel
2010-07-18 15:07 ` Avi Kivity
2010-07-13 2:25 ` [PATCH 16/18] Use getnsboottime in KVM Zachary Amsden
2010-07-15 2:43 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 17/18] Indicate reliable TSC in kvmclock Zachary Amsden
2010-07-15 2:44 ` Rik van Riel
2010-07-13 2:25 ` [PATCH 18/18] Add timekeeping documentation Zachary Amsden
2010-07-14 7:16 ` Takuya Yoshikawa
2010-07-14 20:28 ` Zachary Amsden
2010-07-16 13:19 ` KVM timekeeping fixes, V2 Joerg Roedel
2010-07-16 17:20 ` Zachary Amsden
2010-07-16 19:26 ` Joerg Roedel
2010-07-18 14:22 ` Avi Kivity
2010-07-18 15:08 ` Avi Kivity
2010-07-19 8:11 ` Zachary Amsden
-- strict thread matches above, loose matches on Subject: below --
2010-07-13 2:07 KVM timekeeping fixes Zachary Amsden
2010-07-13 2:08 ` [PATCH 14/18] Fix a possible backwards warp of kvmclock Zachary Amsden
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=1278987938-23873-15-git-send-email-zamsden@redhat.com \
--to=zamsden@redhat.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@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;
as well as URLs for NNTP newsgroup(s).