From bbe6a104e5f02364d973ec6dd27667890573bf45 Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <firstname.lastname@example.org>
Date: Wed, 2 Mar 2011 20:07:48 +0000
Subject: [PATCH 3/4] KVM: x86: Fix kvmclock bug
Backport of commit 28e4639adf0c9f26f6bb56149b7ab547bf33bb95
If preempted after kvmclock values are updated, but before hardware
virtualization is entered, the last tsc time as read by the guest is
never set. It underflows the next time kvmclock is updated if there
has not yet been a successful entry / exit into hardware virt.
Fix this by simply setting last_tsc to the newly read tsc value so
that any computed nsec advance of kvmclock is nulled.
Mar 8: Address feedback from Stefan:
Move back setting of vcpu->last_guest_tsc.
Signed-off-by: Zachary Amsden <email@example.com>
Signed-off-by: Marcelo Tosatti <firstname.lastname@example.org>
Signed-off-by: Serge E. Hallyn <email@example.com>
arch/x86/kvm/x86.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
@@ -694,6 +694,7 @@ static void kvm_write_guest_time(struct kvm_vcpu *v)
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->last_guest_tsc = tsc_timestamp;
* The interface expects us to write an even number signaling that the