All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: Jim Mattson <jmattson@google.com>,
	kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	Peter Shier <pshier@google.com>
Subject: Re: [kvm-unit-tests PATCH] x86: VMX: Add a VMX-preemption timer expiration test
Date: Mon, 12 Oct 2020 09:32:21 -0700	[thread overview]
Message-ID: <20201012163219.GC26135@linux.intel.com> (raw)
In-Reply-To: <D121A03E-6861-4736-8070-5D1E4FEE1D32@gmail.com>

On Sat, Oct 10, 2020 at 01:42:26AM -0700, Nadav Amit wrote:
> > 
> > On May 8, 2020, at 1:39 PM, Jim Mattson <jmattson@google.com> wrote:
> > 
> > When the VMX-preemption timer is activated, code executing in VMX
> > non-root operation should never be able to record a TSC value beyond
> > the deadline imposed by adding the scaled VMX-preemption timer value
> > to the first TSC value observed by the guest after VM-entry.
> > 
> > Signed-off-by: Jim Mattson <jmattson@google.com>
> > Reviewed-by: Peter Shier <pshier@google.com>
> 
> This test failed on my bare-metal machine (Broadwell):
> 
> Test suite: vmx_preemption_timer_expiry_test
> FAIL: Last stored guest TSC (44435478250637180) < TSC deadline (44435478250419552)
> 
> Any hints why, perhaps based on the motivation for the test?

This test also fails intermittently on my Haswell and Coffee Lake systems when
running on KVM.  I haven't done any "debug" beyond a quick glance at the test.

The intent of the test is to verify that KVM injects preemption timer VM-Exits
without violating the architectural guarantees of the timer, e.g. that the exit
isn't delayed by something else happening in the system.

  reply	other threads:[~2020-10-12 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 20:39 [kvm-unit-tests PATCH] x86: VMX: Add a VMX-preemption timer expiration test Jim Mattson
2020-05-09 13:26 ` Paolo Bonzini
2020-10-10  8:42 ` Nadav Amit
2020-10-12 16:32   ` Sean Christopherson [this message]
2020-10-12 16:47     ` Nadav Amit
2020-10-12 17:55       ` Jim Mattson
2020-10-12 18:17         ` Nadav Amit
2020-10-12 18:29           ` Paolo Bonzini
2020-10-12 18:31             ` Nadav Amit
2020-10-12 18:46               ` Jim Mattson
2020-10-12 20:21                 ` Nadav Amit
2020-10-12 18:34             ` Jim Mattson

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=20201012163219.GC26135@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=nadav.amit@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=pshier@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 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.