From: Sean Christopherson <seanjc@google.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] KVM: nVMX: Don't use Enlightened MSR Bitmap for L3
Date: Fri, 5 Nov 2021 00:52:14 +0000 [thread overview]
Message-ID: <YYSAPotqLVIScunK@google.com> (raw)
In-Reply-To: <20211013142258.1738415-2-vkuznets@redhat.com>
On Wed, Oct 13, 2021, Vitaly Kuznetsov wrote:
> 3-level nesting is also not a very common setup nowadays.
Says who? :-D
> Don't enable 'Enlightened MSR Bitmap' feature for KVM's L2s (real L3s) for
> now.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
> ---
> arch/x86/kvm/vmx/vmx.c | 21 ++++++++++++---------
> 1 file changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index 1c8b2b6e7ed9..e82cdde58119 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -2655,15 +2655,6 @@ int alloc_loaded_vmcs(struct loaded_vmcs *loaded_vmcs)
> if (!loaded_vmcs->msr_bitmap)
> goto out_vmcs;
> memset(loaded_vmcs->msr_bitmap, 0xff, PAGE_SIZE);
> -
> - if (IS_ENABLED(CONFIG_HYPERV) &&
> - static_branch_unlikely(&enable_evmcs) &&
> - (ms_hyperv.nested_features & HV_X64_NESTED_MSR_BITMAP)) {
> - struct hv_enlightened_vmcs *evmcs =
> - (struct hv_enlightened_vmcs *)loaded_vmcs->vmcs;
> -
> - evmcs->hv_enlightenments_control.msr_bitmap = 1;
> - }
> }
>
> memset(&loaded_vmcs->host_state, 0, sizeof(struct vmcs_host_state));
> @@ -6903,6 +6894,18 @@ static int vmx_create_vcpu(struct kvm_vcpu *vcpu)
>
> vmx->loaded_vmcs = &vmx->vmcs01;
>
> + /*
> + * Use Hyper-V 'Enlightened MSR Bitmap' feature when KVM runs as a
> + * nested (L1) hypervisor and Hyper-V in L0 supports it.
And maybe call out specifically that KVM intentionally uses this only for vmcs02?
> + */
> + if (IS_ENABLED(CONFIG_HYPERV) && static_branch_unlikely(&enable_evmcs)
> + && (ms_hyperv.nested_features & HV_X64_NESTED_MSR_BITMAP)) {
&& on the previous line, I think we'll survive the 82 char line :-)
> + struct hv_enlightened_vmcs *evmcs =
> + (struct hv_enlightened_vmcs *)vmx->loaded_vmcs->vmcs;
Hmm, what about landing this right after vmcs01's VMCS is allocated? It's kinda
weird, but it makes it more obvious that ->vmcs is not NULL. And if the cast is
simply via a "void *" it all fits on one line.
err = alloc_loaded_vmcs(&vmx->vmcs01);
if (err < 0)
goto free_pml;
/*
* Use Hyper-V 'Enlightened MSR Bitmap' feature when KVM runs as a
* nested (L1) hypervisor and Hyper-V in L0 supports it. Enable an
* enlightened bitmap only for vmcs01, KVM currently isn't equipped to
* realize any performance benefits from enabling it for vmcs02.
*/
if (IS_ENABLED(CONFIG_HYPERV) && static_branch_unlikely(&enable_evmcs) &&
(ms_hyperv.nested_features & HV_X64_NESTED_MSR_BITMAP)) {
struct hv_enlightened_vmcs *evmcs = (void *)vmx->vmcs01.vmcs;
evmcs->hv_enlightenments_control.msr_bitmap = 1;
}
> +
> + evmcs->hv_enlightenments_control.msr_bitmap = 1;
> + }
> +
> if (cpu_need_virtualize_apic_accesses(vcpu)) {
> err = alloc_apic_access_page(vcpu->kvm);
> if (err)
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-11-05 0:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 14:22 [PATCH v3 0/4] KVM: nVMX: Enlightened MSR Bitmap feature for Hyper-V on KVM Vitaly Kuznetsov
2021-10-13 14:22 ` [PATCH v3 1/4] KVM: nVMX: Don't use Enlightened MSR Bitmap for L3 Vitaly Kuznetsov
2021-11-05 0:52 ` Sean Christopherson [this message]
2021-11-05 12:03 ` Vitaly Kuznetsov
2021-11-05 15:38 ` Maxim Levitsky
2021-11-05 15:39 ` Maxim Levitsky
2021-10-13 14:22 ` [PATCH v3 2/4] KVM: VMX: Introduce vmx_msr_bitmap_l01_changed() helper Vitaly Kuznetsov
2021-11-05 1:00 ` Sean Christopherson
2021-10-13 14:22 ` [PATCH v3 3/4] KVM: nVMX: Track whether changes in L0 require MSR bitmap for L2 to be rebuilt Vitaly Kuznetsov
2021-11-05 1:05 ` Sean Christopherson
2021-11-05 12:06 ` Vitaly Kuznetsov
2021-11-05 14:28 ` Sean Christopherson
2021-10-13 14:22 ` [PATCH v3 4/4] KVM: nVMX: Implement Enlightened MSR Bitmap feature Vitaly Kuznetsov
2021-11-05 1:09 ` Sean Christopherson
2021-11-05 12:08 ` Vitaly Kuznetsov
2021-11-03 15:13 ` [PATCH v3 0/4] KVM: nVMX: Enlightened MSR Bitmap feature for Hyper-V on KVM Vitaly Kuznetsov
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=YYSAPotqLVIScunK@google.com \
--to=seanjc@google.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=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 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.