From: Paolo Bonzini <pbonzini@redhat.com>
To: Owen Hofmann <osh@google.com>, kvm@vger.kernel.org
Cc: mtosatti@redhat.com
Subject: Re: [PATCH] kvm: x86: Fix kvm clock versioning.
Date: Thu, 06 Nov 2014 11:52:22 +0100 [thread overview]
Message-ID: <545B52E6.2000503@redhat.com> (raw)
In-Reply-To: <1415062638-26950-1-git-send-email-osh@google.com>
On 04/11/2014 01:57, Owen Hofmann wrote:
> kvm updates the version number for the guest paravirt clock structure by
> incrementing the version of its private copy. It does not read the guest
> version, so will write version = 2 in the first update for every new VM,
> including after restoring a saved state. If guest state is saved during
> reading the clock, it could read and accept struct fields and guest TSC
> from two different updates. This changes the code to increment the guest
> version and write it back.
>
> Signed-off-by: Owen Hofmann <osh@google.com>
> ---
> arch/x86/kvm/x86.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 0033df3..c25c9d8 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -1637,16 +1637,16 @@ static int kvm_guest_time_update(struct kvm_vcpu *v)
> vcpu->hv_clock.system_time = kernel_ns + v->kvm->arch.kvmclock_offset;
> vcpu->last_guest_tsc = tsc_timestamp;
>
> + if (unlikely(kvm_read_guest_cached(v->kvm, &vcpu->pv_time,
> + &guest_hv_clock, sizeof(guest_hv_clock))))
> + return 0;
> +
> /*
> * The interface expects us to write an even number signaling that the
> * update is finished. Since the guest won't see the intermediate
> * state, we just increase by 2 at the end.
> */
> - vcpu->hv_clock.version += 2;
> -
> - if (unlikely(kvm_read_guest_cached(v->kvm, &vcpu->pv_time,
> - &guest_hv_clock, sizeof(guest_hv_clock))))
> - return 0;
> + vcpu->hv_clock.version = guest_hv_clock.version + 2;
>
> /* retain PVCLOCK_GUEST_STOPPED if set in guest copy */
> pvclock_flags = (guest_hv_clock.flags & PVCLOCK_GUEST_STOPPED);
>
Applied, thanks.
Paolo
prev parent reply other threads:[~2014-11-06 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 0:57 [PATCH] kvm: x86: Fix kvm clock versioning Owen Hofmann
2014-11-05 0:12 ` Marcelo Tosatti
2014-11-06 10:52 ` Paolo Bonzini [this message]
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=545B52E6.2000503@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=osh@google.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