kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nadav Amit <nadav.amit@gmail.com>
To: Jim Mattson <jmattson@google.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
	KVM <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 11:17:22 -0700	[thread overview]
Message-ID: <E545AD34-A593-4753-9F22-A36D99BFFE10@gmail.com> (raw)
In-Reply-To: <CALMp9eTkDOCkHaWrqYXKvOuZG4NheSwEgiqGzjwAt6fAdC1Z4A@mail.gmail.com>

> On Oct 12, 2020, at 10:55 AM, Jim Mattson <jmattson@google.com> wrote:
> 
> I don't know of any relevant hardware errata. The test verifies that
> the implementation adheres to the architectural specification.
> 
> KVM clearly doesn't adhere to the architectural specification. I don't
> know what is wrong with your Broadwell machine.

Are you saying that the test is expected to fail on KVM? And that Sean’s
failures are expected?


  reply	other threads:[~2020-10-12 18:17 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
2020-10-12 16:47     ` Nadav Amit
2020-10-12 17:55       ` Jim Mattson
2020-10-12 18:17         ` Nadav Amit [this message]
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=E545AD34-A593-4753-9F22-A36D99BFFE10@gmail.com \
    --to=nadav.amit@gmail.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pshier@google.com \
    --cc=sean.j.christopherson@intel.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).