All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanpeng Li <kernellwp@gmail.com>
To: Liran Alon <LIRAN.ALON@oracle.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Radim Krcmar <rkrcmar@redhat.com>, kvm <kvm@vger.kernel.org>,
	idan.brown@oracle.com,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] KVM: x86: pvclock: Handle first-time write to pvclock-page contains random junk
Date: Mon, 13 Nov 2017 08:52:29 +0800	[thread overview]
Message-ID: <CANRm+Cy9oaG-DU_0pYpvvcKoDTRPiar+HdG-rrEK9EnWn2-sKg@mail.gmail.com> (raw)
In-Reply-To: <5A08EAEA.9060701@ORACLE.COM>

2017-11-13 8:44 GMT+08:00 Liran Alon <LIRAN.ALON@oracle.com>:
>
>
> On 13/11/17 02:40, Wanpeng Li wrote:
>>
>> 2017-11-05 22:11 GMT+08:00 Liran Alon <liran.alon@oracle.com>:
>>>
>>> When guest passes KVM it's pvclock-page GPA via WRMSR to
>>> MSR_KVM_SYSTEM_TIME / MSR_KVM_SYSTEM_TIME_NEW, KVM don't initialize
>>> pvclock-page to some start-values. It just requests a clock-update which
>>
>>
>> KVM does, please refer to memset(hv_clock, 0, size) in kvmclock_init().
>
>
> kvmclock_init() is the code that runs in KVM-guest. I was talking here about
> the code that handles the WRMSR in KVM hypervisor code.
>
> The issue happens when the guest doesn't init pvclock-page as done in
> kvmclock_init(). Not all guests behave nicely :)

But the codes which you modify just works for kvm guest I think.

Regards,
Wanpeng Li

>
> -Liran
>
>>
>> Regards,
>> Wanpeng Li
>>
>>> will happen before entering to guest.
>>>
>>> The clock-update logic will call kvm_setup_pvclock_page() to update the
>>> pvclock-page with info. However, kvm_setup_pvclock_page() *wrongly*
>>> assumes that the version-field is initialized to an even number. This is
>>> wrong because at first-time write, field could be any-value.
>>>
>>> Fix simply makes sure that if first-time version-field is odd, increment
>>> it once more to make it even and only then start standard logic.
>>> This follows same logic as done in other pvclock shared-pages (See
>>> kvm_write_wall_clock() and record_steal_time()).
>>>
>>> Signed-off-by: Liran Alon <liran.alon@oracle.com>
>>> Reviewed-by: Nikita Leshenko <nikita.leshchenko@oracle.com>
>>> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>> ---
>>>   arch/x86/kvm/x86.c | 3 +++
>>>   1 file changed, 3 insertions(+)
>>>
>>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>>> index 03869eb7fcd6..181106080e41 100644
>>> --- a/arch/x86/kvm/x86.c
>>> +++ b/arch/x86/kvm/x86.c
>>> @@ -1830,6 +1830,9 @@ static void kvm_setup_pvclock_page(struct kvm_vcpu
>>> *v)
>>>           */
>>>          BUILD_BUG_ON(offsetof(struct pvclock_vcpu_time_info, version) !=
>>> 0);
>>>
>>> +       if (guest_hv_clock.version & 1)
>>> +               ++guest_hv_clock.version;  /* first time write, random
>>> junk */
>>> +
>>>          vcpu->hv_clock.version = guest_hv_clock.version + 1;
>>>          kvm_write_guest_cached(v->kvm, &vcpu->pv_time,
>>>                                  &vcpu->hv_clock,
>>> --
>>> 1.9.1
>>>
>

  reply	other threads:[~2017-11-13  0:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 14:11 [PATCH] KVM: x86: pvclock: Handle first-time write to pvclock-page contains random junk Liran Alon
2017-11-06  9:13 ` Paolo Bonzini
2017-11-10 21:36 ` Radim Krčmář
2017-11-13  0:40 ` Wanpeng Li
2017-11-13  0:44   ` Liran Alon
2017-11-13  0:52     ` Wanpeng Li [this message]
2017-11-13  0:55       ` Liran Alon
2017-11-13  1:03         ` Wanpeng Li
2017-11-13  1:37           ` Wanpeng Li
2017-11-13  5:53             ` Wanpeng Li

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=CANRm+Cy9oaG-DU_0pYpvvcKoDTRPiar+HdG-rrEK9EnWn2-sKg@mail.gmail.com \
    --to=kernellwp@gmail.com \
    --cc=LIRAN.ALON@oracle.com \
    --cc=idan.brown@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.