From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: 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: Re: [PATCH 1/3] KVM: VMX: Always VMCLEAR in-use VMCSes during crash with kexec support
Date: Fri, 28 Feb 2020 06:59:43 -0800 [thread overview]
Message-ID: <20200228145942.GA2329@linux.intel.com> (raw)
In-Reply-To: <9edc8cef-9aa4-11ca-f8f2-a1fea990b87e@redhat.com>
On Fri, Feb 28, 2020 at 11:16:10AM +0100, Paolo Bonzini wrote:
> On 27/02/20 23:30, Sean Christopherson wrote:
> > -void loaded_vmcs_init(struct loaded_vmcs *loaded_vmcs)
> > +void loaded_vmcs_init(struct loaded_vmcs *loaded_vmcs, bool in_use)
> > {
> > vmcs_clear(loaded_vmcs->vmcs);
> > if (loaded_vmcs->shadow_vmcs && loaded_vmcs->launched)
> > vmcs_clear(loaded_vmcs->shadow_vmcs);
> > +
> > + if (in_use) {
> > + list_del(&loaded_vmcs->loaded_vmcss_on_cpu_link);
> > +
> > + /*
> > + * Ensure deleting loaded_vmcs from its current percpu list
> > + * completes before setting loaded_vmcs->vcpu to -1, otherwise
> > + * a different cpu can see vcpu == -1 first and add loaded_vmcs
> > + * to its percpu list before it's deleted from this cpu's list.
> > + * Pairs with the smp_rmb() in vmx_vcpu_load_vmcs().
> > + */
> > + smp_wmb();
> > + }
> > +
>
> I'd like to avoid the new in_use argument and, also, I think it's a
> little bit nicer to always invoke the memory barrier. Even though we
> use "asm volatile" for vmclear and therefore the compiler is already
> taken care of, in principle it's more correct to order the ->cpu write
> against vmclear's.
Completely agree on all points. I wanted to avoid in_use as well, but it
didn't occur to me to use list_empty()...
> This gives the following patch on top:
Looks good.
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index c9d6152e7a4d..77a64110577b 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -656,25 +656,24 @@ static int vmx_set_guest_msr(struct vcpu_vmx *vmx, struct shared_msr_entry *msr,
> return ret;
> }
>
> -void loaded_vmcs_init(struct loaded_vmcs *loaded_vmcs, bool in_use)
> +void loaded_vmcs_init(struct loaded_vmcs *loaded_vmcs)
> {
> vmcs_clear(loaded_vmcs->vmcs);
> if (loaded_vmcs->shadow_vmcs && loaded_vmcs->launched)
> vmcs_clear(loaded_vmcs->shadow_vmcs);
>
> - if (in_use) {
> + if (!list_empty(&loaded_vmcs->loaded_vmcss_on_cpu_link))
> list_del(&loaded_vmcs->loaded_vmcss_on_cpu_link);
>
> - /*
> - * Ensure deleting loaded_vmcs from its current percpu list
> - * completes before setting loaded_vmcs->vcpu to -1, otherwise
> - * a different cpu can see vcpu == -1 first and add loaded_vmcs
> - * to its percpu list before it's deleted from this cpu's list.
> - * Pairs with the smp_rmb() in vmx_vcpu_load_vmcs().
> - */
> - smp_wmb();
> - }
> -
> + /*
> + * Ensure all writes to loaded_vmcs, including deleting it
> + * from its current percpu list, complete before setting
> + * loaded_vmcs->vcpu to -1; otherwise,, a different cpu can
> + * see vcpu == -1 first and add loaded_vmcs to its percpu
> + * list before it's deleted from this cpu's list. Pairs
> + * with the smp_rmb() in vmx_vcpu_load_vmcs().
> + */
> + smp_wmb();
> loaded_vmcs->cpu = -1;
> loaded_vmcs->launched = 0;
> }
> @@ -701,7 +700,7 @@ static void __loaded_vmcs_clear(void *arg)
> if (per_cpu(current_vmcs, cpu) == loaded_vmcs->vmcs)
> per_cpu(current_vmcs, cpu) = NULL;
>
> - loaded_vmcs_init(loaded_vmcs, true);
> + loaded_vmcs_init(loaded_vmcs);
> }
>
> void loaded_vmcs_clear(struct loaded_vmcs *loaded_vmcs)
> @@ -2568,7 +2567,8 @@ int alloc_loaded_vmcs(struct loaded_vmcs *loaded_vmcs)
>
> loaded_vmcs->shadow_vmcs = NULL;
> loaded_vmcs->hv_timer_soft_disabled = false;
> - loaded_vmcs_init(loaded_vmcs, false);
> + INIT_LIST_HEAD(&loaded_vmcs->loaded_vmcss_on_cpu_link);
> + loaded_vmcs_init(loaded_vmcs);
>
> if (cpu_has_vmx_msr_bitmap()) {
> loaded_vmcs->msr_bitmap = (unsigned long *)
>
> Paolo
>
next prev parent reply other threads:[~2020-02-28 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 22:30 [PATCH 0/3] KVM: VMX: Fix for kexec VMCLEAR and VMXON cleanup Sean Christopherson
2020-02-27 22:30 ` [PATCH 1/3] KVM: VMX: Always VMCLEAR in-use VMCSes during crash with kexec support Sean Christopherson
2020-02-28 10:16 ` Paolo Bonzini
2020-02-28 14:59 ` Sean Christopherson [this message]
2020-03-21 14:55 ` Sean Christopherson
2020-02-27 22:30 ` [PATCH 2/3] KVM: VMX: Gracefully handle faults on VMXON Sean Christopherson
2020-02-27 22:30 ` [PATCH 3/3] KVM: VMX: Make loaded_vmcs_init() a static function Sean Christopherson
2020-02-28 11:02 ` [PATCH 0/3] KVM: VMX: Fix for kexec VMCLEAR and VMXON cleanup 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=20200228145942.GA2329@linux.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