From: Sean Christopherson <sean.j.christopherson@intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: kvm@vger.kernel.org, Krish Sadhukhan <krish.sadhukhan@oracle.com>,
Karl Heubaum <karl.heubaum@oracle.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Jim Mattson <jmattson@google.com>
Subject: [PATCH v6 0/7] KVM: nVMX Add IA32_PAT consistency checks
Date: Thu, 11 Apr 2019 12:18:02 -0700 [thread overview]
Message-ID: <20190411191809.8131-1-sean.j.christopherson@intel.com> (raw)
This is a continuation of Krish's series, which has suffered a teeny
tiny bit of scope creep (sorry Krish). This is essentially a new series,
e.g. only the actual PAT-related patches, which haven't changed since v2,
are retained from previous versions. But, to avoid unnecessary conflicts
I'm resending everything in one happy series.
The direction change relative to v5 is to self-document the top-level
consistency check functions by a) renaming the functions and b) using a
dedicated parameter to "return" the failure information, as suggested by
Paolo. Previous versions had been taking the approach of using the return
value itself to document that a failed "postreqs" leads to a VM-Exit,
which was simply putting lipstick on a pig.
Krish Sadhukhan (2):
Check "load IA32_PAT" VM-exit control on vmentry
Check "load IA32_PAT" VM-entry control on vmentry
Sean Christopherson (5):
KVM: nVMX: Move guest non-reg state checks to VM-Exit path
KVM: nVMX: Rename and split top-level consistency checks to match SDM
KVM: nVMX: Set VM-{Fail,Exit} failure info via params, not return val
KVM: nVMX: Collapse nested_check_host_control_regs() into its caller
KVM: nVMX: Return -EINVAL when signaling failure in VM-Entry helpers
arch/x86/kvm/vmx/nested.c | 150 +++++++++++++++++++++-----------------
1 file changed, 82 insertions(+), 68 deletions(-)
--
2.21.0
next reply other threads:[~2019-04-11 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 19:18 Sean Christopherson [this message]
2019-04-11 19:18 ` [PATCH v6 1/7] Check "load IA32_PAT" VM-exit control on vmentry Sean Christopherson
2019-04-11 19:18 ` [PATCH v6 2/7] Check "load IA32_PAT" VM-entry " Sean Christopherson
2019-04-11 19:18 ` [PATCH v6 3/7] KVM: nVMX: Move guest non-reg state checks to VM-Exit path Sean Christopherson
2019-04-11 21:00 ` Krish Sadhukhan
2019-04-11 19:18 ` [PATCH v6 4/7] KVM: nVMX: Rename and split top-level consistency checks to match SDM Sean Christopherson
2019-04-11 21:23 ` Krish Sadhukhan
2019-04-11 19:18 ` [PATCH v6 5/7] KVM: nVMX: Set VM-{Fail,Exit} failure info via params, not return val Sean Christopherson
2019-04-11 21:56 ` Krish Sadhukhan
2019-04-12 8:30 ` Paolo Bonzini
2019-04-12 19:12 ` Sean Christopherson
2019-04-11 19:18 ` [PATCH v6 6/7] KVM: nVMX: Collapse nested_check_host_control_regs() into its caller Sean Christopherson
2019-04-11 22:02 ` Krish Sadhukhan
2019-04-11 19:18 ` [PATCH v6 7/7] KVM: nVMX: Return -EINVAL when signaling failure in VM-Entry helpers 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=20190411191809.8131-1-sean.j.christopherson@intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jmattson@google.com \
--cc=karl.heubaum@oracle.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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