From: Nadav Amit <nadav.amit@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Nadav Amit <nadav.amit@gmail.com>,
Jim Mattson <jmattson@google.com>,
Sean Christopherson <sean.j.christopherson@intel.com>
Subject: [kvm-unit-tests PATCH 0/2] x86: nVMX: Fix NMI/INTR-window tests
Date: Wed, 8 May 2019 03:27:13 -0700 [thread overview]
Message-ID: <20190508102715.685-1-namit@vmware.com> (raw)
From: Nadav Amit <nadav.amit@gmail.com>
The NMI/INTR-window test in VMX have a couple of bugs. The first bug is
clearly a test issue (and a KVM bug), and is fixed by the first patch.
The second bug is more interesting, and looks as a silicon bug (or
documentation bug, as Intel likes to call them). The second patch just
ensures that a failure of the test would allow the next tests to run.
Cc: Jim Mattson <jmattson@google.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Nadav Amit (2):
x86: nVMX: Use #DB in nmi and intr tests
x86: nVMX: Set guest as active after NMI/INTR-window tests
x86/vmx_tests.c | 74 +++++++++++++++++++++++++------------------------
1 file changed, 38 insertions(+), 36 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-08 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 10:27 Nadav Amit [this message]
2019-05-08 10:27 ` [kvm-unit-tests PATCH 1/2] x86: nVMX: Use #DB in nmi and intr tests Nadav Amit
2019-05-08 23:11 ` Jim Mattson
2019-05-08 23:35 ` Nadav Amit
2019-05-20 15:52 ` Paolo Bonzini
2019-05-20 16:39 ` Nadav Amit
2019-05-20 17:21 ` Paolo Bonzini
2019-05-08 10:27 ` [kvm-unit-tests PATCH 2/2] x86: nVMX: Set guest as active after NMI/INTR-window tests Nadav Amit
2019-05-08 23:21 ` Jim Mattson
2019-05-08 23:38 ` Nadav Amit
2019-05-09 20:48 ` Sean Christopherson
2019-05-09 20:32 ` Sean Christopherson
2019-05-09 21:29 ` Nadav Amit
2019-05-15 16:57 ` Sean Christopherson
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=20190508102715.685-1-namit@vmware.com \
--to=nadav.amit@gmail.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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