All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>,
	Maxim Levitsky <mlevitsk@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/8] KVM: nVMX: Enlightened MSR Bitmap feature for Hyper-V on KVM (+ KVM: x86: MSR filtering and related fixes)
Date: Tue,  9 Nov 2021 17:28:27 +0100	[thread overview]
Message-ID: <20211109162835.99475-1-vkuznets@redhat.com> (raw)

This series combines "Enlightened MSR Bitmap feature for Hyper-V on KVM v4"
and Sean's "KVM: x86: MSR filtering and related fixes v4" 
(https://lore.kernel.org/kvm/20211109013047.2041518-1-seanjc@google.com/)
series as they're code dependent.

Changes in "Enlightened MSR Bitmap feature for Hyper-V on KVM v4" since
 v3 [Sean]:
- Move Hyper-V Enlightened MSR Bitmap in vmx_create_vcpu() and expand
  the comment.
- Add R-b tag to "KVM: VMX: Introduce vmx_msr_bitmap_l01_changed() helper".
- s,msr_bitmap_force_recalc,force_msr_bitmap_recalc,
- Drop unneeded 'out_clear_msr_bitmap_force_recalc' path from "KVM: nVMX:
  Implement Enlightened MSR Bitmap feature".

Original description of the feature:

Updating MSR bitmap for L2 is not cheap and rearly needed. TLFS for Hyper-V
offers 'Enlightened MSR Bitmap' feature which allows L1 hypervisor to
inform L0 when it changes MSR bitmap, this eliminates the need to examine
L1's MSR bitmap for L2 every time when 'real' MSR bitmap for L2 gets
constructed.

When the feature is enabled for Win10+WSL2, it shaves off around 700 CPU
cycles from a nested vmexit cost (tight cpuid loop test).

First patch of the series is unrelated to the newly implemented feature,
it fixes a bug in Enlightened MSR Bitmap usage when KVM runs as a nested
hypervisor on top of Hyper-V.

Sean Christopherson (4):
  KVM: nVMX: Query current VMCS when determining if MSR bitmaps are in
    use
  KVM: nVMX: Handle dynamic MSR intercept toggling
  KVM: VMX: Macrofy the MSR bitmap getters and setters
  KVM: nVMX: Clean up x2APIC MSR handling for L2

Vitaly Kuznetsov (4):
  KVM: nVMX: Don't use Enlightened MSR Bitmap for L3
  KVM: VMX: Introduce vmx_msr_bitmap_l01_changed() helper
  KVM: nVMX: Track whether changes in L0 require MSR bitmap for L2 to be
    rebuilt
  KVM: nVMX: Implement Enlightened MSR Bitmap feature

 arch/x86/kvm/hyperv.c     |   2 +
 arch/x86/kvm/vmx/nested.c | 177 +++++++++++++++++---------------------
 arch/x86/kvm/vmx/vmx.c    |  94 +++++++-------------
 arch/x86/kvm/vmx/vmx.h    |  37 ++++++++
 4 files changed, 149 insertions(+), 161 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-11-09 16:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 16:28 Vitaly Kuznetsov [this message]
2021-11-09 16:28 ` [PATCH v4 1/8] KVM: nVMX: Query current VMCS when determining if MSR bitmaps are in use Vitaly Kuznetsov
2021-11-09 16:28 ` [PATCH v4 2/8] KVM: nVMX: Handle dynamic MSR intercept toggling Vitaly Kuznetsov
2021-11-09 16:28 ` [PATCH v4 3/8] KVM: VMX: Macrofy the MSR bitmap getters and setters Vitaly Kuznetsov
2021-11-09 16:28 ` [PATCH v4 4/8] KVM: nVMX: Clean up x2APIC MSR handling for L2 Vitaly Kuznetsov
2021-11-09 16:28 ` [PATCH v4 5/8] KVM: nVMX: Don't use Enlightened MSR Bitmap for L3 Vitaly Kuznetsov
2021-11-09 16:28 ` [PATCH v4 6/8] KVM: VMX: Introduce vmx_msr_bitmap_l01_changed() helper Vitaly Kuznetsov
2021-11-09 16:28 ` [PATCH v4 7/8] KVM: nVMX: Track whether changes in L0 require MSR bitmap for L2 to be rebuilt Vitaly Kuznetsov
2021-11-09 16:28 ` [PATCH v4 8/8] KVM: nVMX: Implement Enlightened MSR Bitmap feature Vitaly Kuznetsov
2021-11-09 17:33 ` [PATCH v4 0/8] KVM: nVMX: Enlightened MSR Bitmap feature for Hyper-V on KVM (+ KVM: x86: MSR filtering and related fixes) 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=20211109162835.99475-1-vkuznets@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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 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.