mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jay Zhou <jianjay.zhou@huawei.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, seanjc@google.com,
	vkuznets@redhat.com, weidong.huang@huawei.com,
	wangxinxin.wang@huawei.com, zhuangshengen@huawei.com
Subject: Re: [PATCH] KVM: x86: get smi pending status correctly
Date: Mon, 18 Jan 2021 18:57:51 +0100	[thread overview]
Message-ID: <4b2565ca-83da-c337-ccf3-ee31a28fd605@redhat.com> (raw)
In-Reply-To: <20210118084720.1585-1-jianjay.zhou@huawei.com>

On 18/01/21 09:47, Jay Zhou wrote:
> The injection process of smi has two steps:
> 
>      Qemu                        KVM
> Step1:
>      cpu->interrupt_request &= \
>          ~CPU_INTERRUPT_SMI;
>      kvm_vcpu_ioctl(cpu, KVM_SMI)
> 
>                                  call kvm_vcpu_ioctl_smi() and
>                                  kvm_make_request(KVM_REQ_SMI, vcpu);
> 
> Step2:
>      kvm_vcpu_ioctl(cpu, KVM_RUN, 0)
> 
>                                  call process_smi() if
>                                  kvm_check_request(KVM_REQ_SMI, vcpu) is
>                                  true, mark vcpu->arch.smi_pending = true;
> 
> The vcpu->arch.smi_pending will be set true in step2, unfortunately if
> vcpu paused between step1 and step2, the kvm_run->immediate_exit will be
> set and vcpu has to exit to Qemu immediately during step2 before mark
> vcpu->arch.smi_pending true.
> During VM migration, Qemu will get the smi pending status from KVM using
> KVM_GET_VCPU_EVENTS ioctl at the downtime, then the smi pending status
> will be lost.
> 
> Signed-off-by: Jay Zhou <jianjay.zhou@huawei.com>
> Signed-off-by: Shengen Zhuang <zhuangshengen@huawei.com>
> ---
>   arch/x86/kvm/x86.c | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 9a8969a..9025c76 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -105,6 +105,7 @@
>   
>   static void update_cr8_intercept(struct kvm_vcpu *vcpu);
>   static void process_nmi(struct kvm_vcpu *vcpu);
> +static void process_smi(struct kvm_vcpu *vcpu);
>   static void enter_smm(struct kvm_vcpu *vcpu);
>   static void __kvm_set_rflags(struct kvm_vcpu *vcpu, unsigned long rflags);
>   static void store_regs(struct kvm_vcpu *vcpu);
> @@ -4230,6 +4231,9 @@ static void kvm_vcpu_ioctl_x86_get_vcpu_events(struct kvm_vcpu *vcpu,
>   {
>   	process_nmi(vcpu);
>   
> +	if (kvm_check_request(KVM_REQ_SMI, vcpu))
> +		process_smi(vcpu);
> +
>   	/*
>   	 * In guest mode, payload delivery should be deferred,
>   	 * so that the L1 hypervisor can intercept #PF before
> 

Queued, thanks.

Paolo


      reply	other threads:[~2021-01-18 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18  8:47 Jay Zhou
2021-01-18 17:57 ` Paolo Bonzini [this message]

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=4b2565ca-83da-c337-ccf3-ee31a28fd605@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=vkuznets@redhat.com \
    --cc=wangxinxin.wang@huawei.com \
    --cc=weidong.huang@huawei.com \
    --cc=zhuangshengen@huawei.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

all inboxes | Powered by JetHome®