kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liran Alon <liran.alon@oracle.com>
To: <chao.gao@intel.com>
Cc: <mingo@redhat.com>, <x86@kernel.org>, <tglx@linutronix.de>,
	<rkrcmar@redhat.com>, <pbonzini@redhat.com>,
	<linux-kernel@vger.kernel.org>, <hpa@zytor.com>,
	<kvm@vger.kernel.org>
Subject: Re: [PATCH v3] KVM: VMX: Don't halt vcpu when L1 is injecting events to L2
Date: Sun, 11 Feb 2018 00:51:14 -0800 (PST)	[thread overview]
Message-ID: <3bf7f0af-cfdf-4daa-8230-240e7e63f099@default> (raw)


----- chao.gao@intel.com wrote:

> Although L2 is in halt state, it will be in the active state after
> VM entry if the VM entry is vectoring according to SDM 26.6.2
> Activity
> State. Halting the vcpu here means the event won't be injected to L2
> and this decision isn't reported to L1. Thus L0 drops an event that
> should be injected to L2.
> 
> Cc: Liran Alon <liran.alon@oracle.com>
> Signed-off-by: Chao Gao <chao.gao@intel.com>
> ---
> changes in v3:
>  - s/VECTORING_INFO_VALID_MASK/INTR_INFO_VALID_MASK
>  - Changes of subject, comments.
> 
> Changes in v2:
>  - Remove VID stuff. Only handle event injection in this patch.
> 
> Signed-off-by: Chao Gao <chao.gao@intel.com>
> ---
>  arch/x86/kvm/vmx.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index bb5b488..cf7c2fc 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -10985,7 +10985,12 @@ static int nested_vmx_run(struct kvm_vcpu
> *vcpu, bool launch)
>  	if (ret)
>  		return ret;
>  
> -	if (vmcs12->guest_activity_state == GUEST_ACTIVITY_HLT)
> +	/*
> +	 * If we're entering a halted L2 vcpu and the L2 vcpu won't be
> woken
> +	 * by event injection, halt vcpu.
> +	 */
> +	if ((vmcs12->guest_activity_state == GUEST_ACTIVITY_HLT) &&
> +	    !(vmcs12->vm_entry_intr_info_field & INTR_INFO_VALID_MASK))
>  		return kvm_vcpu_halt(vcpu);
>  
>  	vmx->nested.nested_run_pending = 1;
> -- 
> 1.9.1

Reviewed-by: Liran Alon <liran.alon@oracle.com>

(Paolo: I would recommend changing commit title from "KVM: VMX: ..." to "KVM: nVMX: ..."
when applying for convention. Easier to grep nVMX changes.)

             reply	other threads:[~2018-02-11  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11  8:51 Liran Alon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-11  2:06 [PATCH v3] KVM: VMX: Don't halt vcpu when L1 is injecting events to L2 Chao Gao
2018-02-13 14:38 ` 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=3bf7f0af-cfdf-4daa-8230-240e7e63f099@default \
    --to=liran.alon@oracle.com \
    --cc=chao.gao@intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).