From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Yuan Yao <yuan.yao@linux.intel.com>
Subject: [PATCH 0/3] KVM: x86: Fix goofs with MONITOR/MWAIT quirk
Date: Mon, 11 Jul 2022 22:57:50 +0000 [thread overview]
Message-ID: <20220711225753.1073989-1-seanjc@google.com> (raw)
Fix two bugs in the MONITOR/MWAIT selftest, and tweak the name of the
quirk (which isn't yet set in stone) to clarify that it only applies to
the #UD behavior, i.e. to reserve the right to correctly emulate #GP and
other faults in the future even if the quirk is enabled.
Sean Christopherson (3):
KVM: selftests: Test MONITOR and MWAIT, not just MONITOR for quirk
KVM: selftests: Provide valid inputs for MONITOR/MWAIT regs
KVM: x86: Tweak name of MONITOR/MWAIT #UD quirk to make it #UD
specific
Documentation/virt/kvm/api.rst | 2 +-
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/include/uapi/asm/kvm.h | 2 +-
arch/x86/kvm/x86.c | 2 +-
.../testing/selftests/kvm/x86_64/monitor_mwait_test.c | 10 +++++++---
5 files changed, 11 insertions(+), 7 deletions(-)
base-commit: b9b71f43683ae9d76b0989249607bbe8c9eb6c5c
--
2.37.0.144.g8ac04bfd2-goog
next reply other threads:[~2022-07-11 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 22:57 Sean Christopherson [this message]
2022-07-11 22:57 ` [PATCH 1/3] KVM: selftests: Test MONITOR and MWAIT, not just MONITOR for quirk Sean Christopherson
2022-07-11 22:57 ` [PATCH 2/3] KVM: selftests: Provide valid inputs for MONITOR/MWAIT regs Sean Christopherson
2022-07-11 22:57 ` [PATCH 3/3] KVM: x86: Tweak name of MONITOR/MWAIT #UD quirk to make it #UD specific 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=20220711225753.1073989-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=yuan.yao@linux.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
all inboxes | Powered by JetHome®