From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, "Nadav Amit" <nadav.amit@gmail.com>,
"Liran Alon" <liran.alon@oracle.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>
Subject: Re: [PATCH 06/15] KVM: nVMX: Don't "put" vCPU or host state when switching VMCS
Date: Thu, 6 Jun 2019 11:57:27 -0700 [thread overview]
Message-ID: <20190606185727.GK23169@linux.intel.com> (raw)
In-Reply-To: <79ac3a1c-8386-3f5a-2abd-eb284407abb7@redhat.com>
On Thu, Jun 06, 2019 at 06:24:43PM +0200, Paolo Bonzini wrote:
> On 07/05/19 18:06, Sean Christopherson wrote:
> > When switching between vmcs01 and vmcs02, KVM isn't actually switching
> > between guest and host. If guest state is already loaded (the likely,
> > if not guaranteed, case), keep the guest state loaded and manually swap
> > the loaded_cpu_state pointer after propagating saved host state to the
> > new vmcs0{1,2}.
> >
> > Avoiding the switch between guest and host reduces the latency of
> > switching between vmcs01 and vmcs02 by several hundred cycles, and
> > reduces the roundtrip time of a nested VM by upwards of 1000 cycles.
> >
> > Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
> > ---
> > arch/x86/kvm/vmx/nested.c | 18 +++++++++++++-
> > arch/x86/kvm/vmx/vmx.c | 52 ++++++++++++++++++++++-----------------
> > arch/x86/kvm/vmx/vmx.h | 3 ++-
> > 3 files changed, 48 insertions(+), 25 deletions(-)
> >
> > diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> > index a30d53823b2e..4651d3462df4 100644
> > --- a/arch/x86/kvm/vmx/nested.c
> > +++ b/arch/x86/kvm/vmx/nested.c
> > @@ -241,15 +241,31 @@ static void free_nested(struct kvm_vcpu *vcpu)
> > static void vmx_switch_vmcs(struct kvm_vcpu *vcpu, struct loaded_vmcs *vmcs)
> > {
> > struct vcpu_vmx *vmx = to_vmx(vcpu);
> > + struct vmcs_host_state *src;
> > + struct loaded_vmcs *prev;
> > int cpu;
> >
> > if (vmx->loaded_vmcs == vmcs)
> > return;
> >
> > cpu = get_cpu();
> > - vmx_vcpu_put(vcpu);
> > + prev = vmx->loaded_cpu_state;
> > vmx->loaded_vmcs = vmcs;
> > vmx_vcpu_load(vcpu, cpu);
> > +
> > + if (likely(prev)) {
> > + src = &prev->host_state;
> > +
> > + vmx_set_host_fs_gs(&vmcs->host_state, src->fs_sel, src->gs_sel,
> > + src->fs_base, src->gs_base);
> > +
> > + vmcs->host_state.ldt_sel = src->ldt_sel;
> > +#ifdef CONFIG_X86_64
> > + vmcs->host_state.ds_sel = src->ds_sel;
> > + vmcs->host_state.es_sel = src->es_sel;
> > +#endif
> > + vmx->loaded_cpu_state = vmcs;
> > + }
> > put_cpu();
>
> I'd like to extract this into a separate function:
>
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index 438fae1fef2a..83e436f201bf 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -248,34 +248,40 @@ static void free_nested(struct kvm_vcpu *vcpu)
> free_loaded_vmcs(&vmx->nested.vmcs02);
> }
>
> +static void vmx_sync_vmcs_host_state(struct vcpu_vmx *vmx)
What about taking the vmcs pointers, and using old/new instead of
prev/cur? Calling it prev is wonky since it's pulled from the current
value of loaded_cpu_state, especially since cur is the same type.
That oddity is also why I grabbed prev before setting loaded_vmcs,
it just felt wrong even though they really are two separate things.
static void vmx_sync_vmcs_host_state(struct vcpu_vmx *vmx,
struct loaded_vmcs *old,
struct loaded_vmcs *new)
{
...
}
{
vmx_sync_vmcs_host_state(vmx, vmx->loaded_cpu_state, vmcs);
}
> +{
> + struct loaded_vmcs *prev = vmx->loaded_cpu_state;
> + struct loaded_vmcs *cur;
> + struct vmcs_host_state *dest, *src;
> +
> + if (unlikely(!prev))
> + return;
> +
> + cur = &vmx->loaded_vmcs;
> + src = &prev->host_state;
> + dest = &cur->host_state;
> +
> + vmx_set_host_fs_gs(dest, src->fs_sel, src->gs_sel, src->fs_base, src->gs_base);
> + dest->ldt_sel = src->ldt_sel;
> +#ifdef CONFIG_X86_64
> + dest->ds_sel = src->ds_sel;
> + dest->es_sel = src->es_sel;
> +#endif
> + vmx->loaded_cpu_state = cur;
> +}
> +
> static void vmx_switch_vmcs(struct kvm_vcpu *vcpu, struct loaded_vmcs *vmcs)
> {
> struct vcpu_vmx *vmx = to_vmx(vcpu);
> - struct vmcs_host_state *src;
> - struct loaded_vmcs *prev;
> int cpu;
>
> if (vmx->loaded_vmcs == vmcs)
> return;
>
> cpu = get_cpu();
> - prev = vmx->loaded_cpu_state;
> vmx->loaded_vmcs = vmcs;
> vmx_vcpu_load(vcpu, cpu);
> -
> - if (likely(prev)) {
> - src = &prev->host_state;
> -
> - vmx_set_host_fs_gs(&vmcs->host_state, src->fs_sel, src->gs_sel,
> - src->fs_base, src->gs_base);
> -
> - vmcs->host_state.ldt_sel = src->ldt_sel;
> -#ifdef CONFIG_X86_64
> - vmcs->host_state.ds_sel = src->ds_sel;
> - vmcs->host_state.es_sel = src->es_sel;
> -#endif
> - vmx->loaded_cpu_state = vmcs;
> - }
> + vmx_sync_vmcs_host_state(vmx);
> put_cpu();
>
> vm_entry_controls_reset_shadow(vmx);
>
> Paolo
next prev parent reply other threads:[~2019-06-06 18:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:06 [PATCH 00/15] KVM: nVMX: Optimize nested VM-Entry Sean Christopherson
2019-05-07 16:06 ` [PATCH 01/15] KVM: nVMX: Don't dump VMCS if virtual APIC page can't be mapped Sean Christopherson
2019-05-07 20:09 ` Paolo Bonzini
2019-05-07 16:06 ` [PATCH 02/15] KVM: VMX: Always signal #GP on WRMSR to MSR_IA32_CR_PAT with bad value Sean Christopherson
2019-05-07 16:06 ` [PATCH 03/15] KVM: nVMX: Always sync GUEST_BNDCFGS when it comes from vmcs01 Sean Christopherson
2019-05-07 16:06 ` [PATCH 04/15] KVM: nVMX: Write ENCLS-exiting bitmap once per vmcs02 Sean Christopherson
2019-05-07 16:06 ` [PATCH 05/15] KVM: nVMX: Don't rewrite GUEST_PML_INDEX during nested VM-Entry Sean Christopherson
2019-06-06 15:49 ` Paolo Bonzini
2019-05-07 16:06 ` [PATCH 06/15] KVM: nVMX: Don't "put" vCPU or host state when switching VMCS Sean Christopherson
2019-06-06 16:24 ` Paolo Bonzini
2019-06-06 18:57 ` Sean Christopherson [this message]
2019-06-07 17:00 ` Paolo Bonzini
2019-06-07 17:08 ` Sean Christopherson
2019-05-07 16:06 ` [PATCH 07/15] KVM: nVMX: Don't reread VMCS-agnostic " Sean Christopherson
2019-05-07 21:01 ` Paolo Bonzini
2019-05-07 16:06 ` [PATCH 08/15] KVM: nVMX: Don't speculatively write virtual-APIC page address Sean Christopherson
2019-05-07 16:06 ` [PATCH 09/15] KVM: nVMX: Don't speculatively write APIC-access " Sean Christopherson
2019-05-07 16:06 ` [PATCH 10/15] KVM: nVMX: Update vmcs12 for MSR_IA32_CR_PAT when it's written Sean Christopherson
2019-05-07 16:06 ` [PATCH 11/15] KVM: nVMX: Update vmcs12 for SYSENTER MSRs when they're written Sean Christopherson
2019-06-06 16:35 ` Paolo Bonzini
2019-05-07 16:06 ` [PATCH 12/15] KVM: nVMX: Update vmcs12 for MSR_IA32_DEBUGCTLMSR when it's written Sean Christopherson
2019-05-07 16:06 ` [PATCH 13/15] KVM: nVMX: Update vmcs02 GUEST_IA32_DEBUGCTL only when vmcs12 is dirty Sean Christopherson
2019-06-06 16:39 ` Paolo Bonzini
2019-05-07 16:06 ` [PATCH 14/15] KVM: nVMX: Don't update GUEST_BNDCFGS if it's clean in HV eVMCS Sean Christopherson
2019-05-07 16:06 ` [PATCH 15/15] KVM: nVMX: Copy PDPTRs to/from vmcs12 only when necessary Sean Christopherson
2019-06-06 16:53 ` Paolo Bonzini
2019-06-06 16:54 ` [PATCH 00/15] KVM: nVMX: Optimize nested VM-Entry 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=20190606185727.GK23169@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=nadav.amit@gmail.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=vkuznets@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