public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Yuki Shibuya <shibuya.yk@ncos.nec.co.jp>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Nobuo Yoshida <yoshida.nb@ncos.nec.co.jp>
Subject: Re: [PATCH] KVM: x86: Inject pending interrupt even if pending nmi exist
Date: Tue, 22 Mar 2016 07:41:52 +0100	[thread overview]
Message-ID: <56F0E930.5030300@siemens.com> (raw)
In-Reply-To: <7CC7D3013F4B10479273CE019E6A8C7A3ED41B@BPXM15GP.gisp.nec.co.jp>

On 2016-03-22 06:28, Yuki Shibuya wrote:
> Non maskable interrupts (NMI) are preferred to interrupts in current
> implementation. If a NMI is pending and NMI is blocked by the result
> of nmi_allowed(), pending interrupt is not injected and
> enable_irq_window() is not executed, even if interrupts injection is
> allowed.
> 
> In old kernel (e.g. 2.6.32), schedule() is often called in NMI context.
> In this case, interrupts are needed to execute iret that intends end
> of NMI. The flag of blocking new NMI is not cleared until the guest
> execute the iret, and interrupts are blocked by pending NMI. Due to
> this, iret can't be invoked in the guest, and the guest is starved
> until block is cleared by some events (e.g. canceling injection).
> 
> This patch injects pending interrupts, when it's allowed, even if NMI
> is blocked. And, if NMI pending count == 2, NMI is not blocked and an
> interrupt is pending, NMI pending count is decremented to execute
> enable_irq_window().

The first part I understand and agree with. But the part after "And"
worries me still: if we can simply decrement that pending counter once
again - why can't we just clear it to 0 in the first place?

BTW, some inline documentation of this tricky logic would probably be good.

Jan

> 
> Signed-off-by: Yuki Shibuya <shibuya.yk@ncos.nec.co.jp>
> ---
>  arch/x86/kvm/x86.c | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 7236bd3..1373627 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -6087,12 +6087,14 @@ static int inject_pending_event(struct kvm_vcpu *vcpu, bool req_int_win)
>  	}
>  
>  	/* try to inject new event if pending */
> -	if (vcpu->arch.nmi_pending) {
> -		if (kvm_x86_ops->nmi_allowed(vcpu)) {
> +	if (vcpu->arch.nmi_pending && kvm_x86_ops->nmi_allowed(vcpu)) {
> +		--vcpu->arch.nmi_pending;
> +		vcpu->arch.nmi_injected = true;
> +		kvm_x86_ops->set_nmi(vcpu);
> +
> +		if (vcpu->arch.nmi_pending && kvm_cpu_has_injectable_intr(vcpu)
> +					&& kvm_x86_ops->interrupt_allowed(vcpu))
>  			--vcpu->arch.nmi_pending;
> -			vcpu->arch.nmi_injected = true;
> -			kvm_x86_ops->set_nmi(vcpu);
> -		}
>  	} else if (kvm_cpu_has_injectable_intr(vcpu)) {
>  		/*
>  		 * Because interrupts can be injected asynchronously, we are
> 

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2016-03-22  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22  5:28 [PATCH] KVM: x86: Inject pending interrupt even if pending nmi exist Yuki Shibuya
2016-03-22  6:41 ` Jan Kiszka [this message]
2016-03-22  7:55   ` Yuki Shibuya
2016-03-23  1:30   ` Yuki Shibuya

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=56F0E930.5030300@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=shibuya.yk@ncos.nec.co.jp \
    --cc=yoshida.nb@ncos.nec.co.jp \
    /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