All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
	kvm@vger.kernel.org, Sean Christopherson <seanjc@google.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH v2 6/4] selftests: kvm: Add basic Hyper-V clocksources tests
Date: Thu, 18 Mar 2021 14:55:15 -0300	[thread overview]
Message-ID: <20210318175515.GA40821@fuller.cnet> (raw)
In-Reply-To: <4882dc8f-30bf-f049-f770-24811bb96b54@redhat.com>

On Thu, Mar 18, 2021 at 06:50:35PM +0100, Paolo Bonzini wrote:
> On 18/03/21 17:57, Marcelo Tosatti wrote:
> > I think this should be monotonically increasing:
> > 
> > 1.	r1 = rdtsc();
> > 2.	t1 = rdmsr(HV_X64_MSR_TIME_REF_COUNT);
> > 3.	nop_loop();
> > 4.	r2 = rdtsc();
> > 5.	t2 = rdmsr(HV_X64_MSR_TIME_REF_COUNT);	
> > 
> > > 
> > > +	/* 1% tolerance */
> > > +	GUEST_ASSERT(delta_ns * 100 < (t2 - t1) * 100);
> > > +}
> > 
> > Doesnt an unbounded schedule-out/schedule-in (which resembles
> > overloaded host) of the qemu-kvm vcpu in any of the points 1,2,3,4,5
> > break the assertion above?
> 
> 
> Yes, there's a window of a handful of instructions (at least on
> non-preemptible kernels).  If anyone ever hits it, we can run the test 100
> times and check that it passes at least 95 or 99 of them.
> 
> Paolo

Yep, sounds like a good solution.

However this makes me wonder on the validity of the test: what its
trying to verify, again? (i would check the monotonicity that 
is r1 <= t1 <= r2 <= t2 as well, without the nop_loop in between).


  reply	other threads:[~2021-03-18 17:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 14:37 [PATCH v2 0/4] KVM: x86: hyper-v: TSC page fixes Vitaly Kuznetsov
2021-03-16 14:37 ` [PATCH v2 1/4] KVM: x86: hyper-v: Limit guest to writing zero to HV_X64_MSR_TSC_EMULATION_STATUS Vitaly Kuznetsov
2021-03-16 14:37 ` [PATCH v2 2/4] KVM: x86: hyper-v: Prevent using not-yet-updated TSC page by secondary CPUs Vitaly Kuznetsov
2021-03-18 17:02   ` Marcelo Tosatti
2021-03-18 18:04     ` Marcelo Tosatti
2021-03-18 18:05       ` Paolo Bonzini
2021-03-18 18:30         ` Marcelo Tosatti
2021-03-19  9:29           ` Vitaly Kuznetsov
2021-03-16 14:37 ` [PATCH v2 3/4] KVM: x86: hyper-v: Track Hyper-V TSC page status Vitaly Kuznetsov
2021-03-17  8:07   ` Paolo Bonzini
2021-03-17 11:19     ` [PATCH v2 5/4] KVM: x86: hyper-v: Briefly document enum hv_tsc_page_status Vitaly Kuznetsov
2021-03-16 14:37 ` [PATCH v2 4/4] KVM: x86: hyper-v: Don't touch TSC page values when guest opted for re-enlightenment Vitaly Kuznetsov
2021-03-18 14:09 ` [PATCH v2 6/4] selftests: kvm: Add basic Hyper-V clocksources tests Vitaly Kuznetsov
2021-03-18 14:26   ` Paolo Bonzini
2021-03-18 14:52     ` Vitaly Kuznetsov
2021-03-18 15:01       ` Paolo Bonzini
2021-03-18 15:23         ` Vitaly Kuznetsov
2021-03-18 15:27   ` Paolo Bonzini
2021-03-18 16:57   ` Marcelo Tosatti
2021-03-18 17:50     ` Paolo Bonzini
2021-03-18 17:55       ` Marcelo Tosatti [this message]
2021-03-19  9:35         ` Vitaly Kuznetsov

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=20210318175515.GA40821@fuller.cnet \
    --to=mtosatti@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.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.