linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, rkrcmar@redhat.com
Subject: Re: [PATCH v3] KVM: x86: do not go through vcpu in __get_kvmclock_ns
Date: Thu, 17 Nov 2016 13:14:35 +0100	[thread overview]
Message-ID: <13d50b94-f884-e976-158a-508bcbcc6fa1@redhat.com> (raw)
In-Reply-To: <20161117113818.GA11473@amt.cnet>



On 17/11/2016 12:38, Marcelo Tosatti wrote:
> On Wed, Nov 16, 2016 at 06:31:30PM +0100, Paolo Bonzini wrote:
>> Going through the first VCPU is wrong if you follow a KVM_SET_CLOCK with
>> a KVM_GET_CLOCK immediately after, without letting the VCPU run and
>> call kvm_guest_time_update.
>>
>> To fix this, compute the kvmclock value ourselves, using the master
>> clock (tsc, nsec) pair as the base and the host CPU frequency as
>> the scale.
>>
>> Reported-by: Marcelo Tosatti <mtosatti@redhat.com>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>>  arch/x86/kvm/x86.c | 21 +++++++++++++--------
>>  1 file changed, 13 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>> index 1ba08278a9a9..bd138a79404a 100644
>> --- a/arch/x86/kvm/x86.c
>> +++ b/arch/x86/kvm/x86.c
>> @@ -1724,18 +1724,23 @@ static void kvm_gen_update_masterclock(struct kvm *kvm)
>>  
>>  static u64 __get_kvmclock_ns(struct kvm *kvm)
>>  {
>> -	struct kvm_vcpu *vcpu = kvm_get_vcpu(kvm, 0);
>>  	struct kvm_arch *ka = &kvm->arch;
>> -	s64 ns;
>> +	struct pvclock_vcpu_time_info hv_clock;
>>  
>> -	if (vcpu->arch.hv_clock.flags & PVCLOCK_TSC_STABLE_BIT) {
>> -		u64 tsc = kvm_read_l1_tsc(vcpu, rdtsc());
>> -		ns = __pvclock_read_cycles(&vcpu->arch.hv_clock, tsc);
>> -	} else {
>> -		ns = ktime_get_boot_ns() + ka->kvmclock_offset;
>> +	spin_lock(&ka->pvclock_gtod_sync_lock);
>> +	if (!ka->use_master_clock) {
>> +		spin_unlock(&ka->pvclock_gtod_sync_lock);
>> +		return ktime_get_boot_ns() + ka->kvmclock_offset;
>>  	}
>>  
>> -	return ns;
>> +	hv_clock.tsc_timestamp = ka->master_cycle_now;
>> +	hv_clock.system_time = ka->master_kernel_ns + ka->kvmclock_offset;
>> +	spin_unlock(&ka->pvclock_gtod_sync_lock);
>> +
>> +	kvm_get_time_scale(NSEC_PER_SEC, __this_cpu_read(cpu_tsc_khz) * 1000LL,
>> +			   &hv_clock.tsc_shift,
>> +			   &hv_clock.tsc_to_system_mul);
>> +	return __pvclock_read_cycles(&hv_clock, rdtsc());
>>  }
> 
> Missing TSC scaling? 
> 
>         /* With all the info we got, fill in the values */
> 
>         if (kvm_has_tsc_control)
>                 tgt_tsc_khz = kvm_scale_tsc(v, tgt_tsc_khz);
> 
> Should use kvm_read_l1_tsc to convert as well?

We don't have a vcpu, so we cannot use either kvm_scale_tsc or
kvm_read_l1_tsc.  But luckily it's not necessary here, because we're
using cpu_tsc_khz and rdtsc.

Paolo

      reply	other threads:[~2016-11-17 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 17:31 [PATCH v3] KVM: x86: do not go through vcpu in __get_kvmclock_ns Paolo Bonzini
2016-11-16 18:13 ` Radim Krčmář
2016-11-17 11:38 ` Marcelo Tosatti
2016-11-17 12:14   ` 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=13d50b94-f884-e976-158a-508bcbcc6fa1@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@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 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).