From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.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
Subject: [PATCH 0/2] KVM: nVMX: Skip IPBP on nested VMCS switch
Date: Wed, 6 May 2020 16:58:48 -0700 [thread overview]
Message-ID: <20200506235850.22600-1-sean.j.christopherson@intel.com> (raw)
Or as Jim would say, "Really skip IPBP on nested VMCS switch" :-D
Patch 1 is the delta between kvm/queue and v3 of the original patch[*],
i.e. I just cherry-picked v3 and fixed the conflicts.
Patch 2 applies the "no IPBP" logic to copy_vmcs02_to_vmcs12_rare().
Feel free to sqaush both of these to commit 7407a52f23732 ("KVM: nVMX:
Skip IBPB when switching between vmcs01 and vmcs02") if you so desire.
[*] https://lkml.kernel.org/r/20200505044644.16563-1-sean.j.christopherson@intel.com
Sean Christopherson (2):
KVM: nVMX: Refactor IBPB handling on VMCS switch to genericize code
KVM: nVMX: Skip IPBP when switching between vmcs01 and vmcs02, redux
arch/x86/kvm/vmx/nested.c | 13 +++----------
arch/x86/kvm/vmx/vmx.c | 19 ++++++++++++++-----
arch/x86/kvm/vmx/vmx.h | 4 ++--
3 files changed, 19 insertions(+), 17 deletions(-)
--
2.26.0
next reply other threads:[~2020-05-06 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 23:58 Sean Christopherson [this message]
2020-05-06 23:58 ` [PATCH 1/2] KVM: nVMX: Refactor IBPB handling on VMCS switch to genericize code Sean Christopherson
2020-05-06 23:58 ` [PATCH 2/2] KVM: nVMX: Skip IPBP when switching between vmcs01 and vmcs02, redux Sean Christopherson
2020-05-07 11:58 ` [PATCH 0/2] KVM: nVMX: Skip IPBP on nested VMCS switch 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=20200506235850.22600-1-sean.j.christopherson@intel.com \
--to=sean.j.christopherson@intel.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 \
/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).