From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: kvm@vger.kernel.org
Cc: rkrcmar@redhat.com, pbonzini@redhat.com, jmattson@google.com
Subject: [PATCH 0/5] KVM: nVMX: Skip vmentry checks that are necessary only if VMCS12 is dirty
Date: Sun, 7 Jul 2019 03:11:42 -0400 [thread overview]
Message-ID: <20190707071147.11651-1-krish.sadhukhan@oracle.com> (raw)
The following functions,
nested_vmx_check_controls
nested_vmx_check_host_state
nested_vmx_check_guest_state
do a number of vmentry checks for VMCS12. However, not all of these checks need
to be executed on every vmentry. This patchset makes some of these vmentry
checks optional based on the state of VMCS12 in that if VMCS12 is dirty, only
then the checks will be executed. This will reduce performance impact on
vmentry of nested guests.
[PATCH 1/5] KVM: nVMX: Skip VM-Execution Control vmentry checks that are
[PATCH 2/5] KVM: nVMX: Skip VM-Exit Control vmentry checks that are
[PATCH 3/5] KVM: nVMX: Skip VM-Entry Control checks that are necessary
[PATCH 4/5] KVM: nVMX: Skip Host State Area vmentry checks that are
[PATCH 5/5] KVM: nVMX: Skip Guest State Area vmentry checks that are
arch/x86/kvm/vmx/nested.c | 149 ++++++++++++++++++++++++++++++++++------------
1 file changed, 111 insertions(+), 38 deletions(-)
Krish Sadhukhan (5):
nVMX: Skip VM-Execution Control vmentry checks that are necessary only if VMCS12 is dirty
nVMX: Skip VM-Exit Control vmentry checks that are necessary only if VMCS12 is dirty
nVMX: Skip VM-Entry Control checks that are necessary only if VMCS12 is dirty
nVMX: Skip Host State Area vmentry checks that are necessary only if VMCS12 is dirty
nVMX: Skip Guest State Area vmentry checks that are necessary only if VMCS12 is dirty
next reply other threads:[~2019-07-07 7:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 7:11 Krish Sadhukhan [this message]
2019-07-07 7:11 ` [PATCH 1/5] KVM: nVMX: Skip VM-Execution Control vmentry checks that are necessary only if VMCS12 is dirty Krish Sadhukhan
2019-07-07 7:11 ` [PATCH 2/5] KVM: nVMX: Skip VM-Exit " Krish Sadhukhan
2019-07-10 14:28 ` Paolo Bonzini
2019-07-10 19:18 ` Krish Sadhukhan
2019-07-10 20:11 ` Sean Christopherson
2019-07-07 7:11 ` [PATCH 3/5] KVM: nVMX: Skip VM-Entry Control " Krish Sadhukhan
2019-07-10 16:28 ` Paolo Bonzini
2019-07-07 7:11 ` [PATCH 4/5] KVM: nVMX: Skip Host State Area vmentry " Krish Sadhukhan
2019-07-10 16:26 ` Paolo Bonzini
2019-07-07 7:11 ` [PATCH 5/5] KVM: nVMX: Skip Guest " Krish Sadhukhan
2019-07-10 16:33 ` Paolo Bonzini
2019-07-10 19:34 ` Krish Sadhukhan
2019-07-08 18:17 ` [PATCH 0/5] KVM: nVMX: Skip " Sean Christopherson
2019-07-09 22:50 ` Krish Sadhukhan
2019-07-10 14:35 ` Paolo Bonzini
2019-07-10 16:15 ` Sean Christopherson
2019-07-10 16:33 ` Paolo Bonzini
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=20190707071147.11651-1-krish.sadhukhan@oracle.com \
--to=krish.sadhukhan@oracle.com \
--cc=jmattson@google.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 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.