From: Paolo Bonzini <pbonzini@redhat.com>
To: Yuki Shibuya <shibuya.yk@ncos.nec.co.jp>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Nobuo Yoshida" <yoshida.nb@ncos.nec.co.jp>
Subject: Re: [PATCH v3] KVM: x86: Inject pending interrupt even if pending nmi exist
Date: Thu, 24 Mar 2016 12:14:30 +0100 [thread overview]
Message-ID: <56F3CC16.4000608@redhat.com> (raw)
In-Reply-To: <7CC7D3013F4B10479273CE019E6A8C7A3EDDB3@BPXM15GP.gisp.nec.co.jp>
On 24/03/2016 06:17, 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 an interrupts is pending after executing
> inject_pending_event(), enable_irq_window() is executed regardless of
> NMI pending counter.
>
> Signed-off-by: Yuki Shibuya <shibuya.yk@ncos.nec.co.jp>
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> arch/x86/kvm/x86.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 7236bd3..d4fd555 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -6087,12 +6087,10 @@ 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)) {
> - --vcpu->arch.nmi_pending;
> - vcpu->arch.nmi_injected = true;
> - kvm_x86_ops->set_nmi(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);
> } else if (kvm_cpu_has_injectable_intr(vcpu)) {
> /*
> * Because interrupts can be injected asynchronously, we are
> @@ -6561,10 +6559,12 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
> if (inject_pending_event(vcpu, req_int_win) != 0)
> req_immediate_exit = true;
> /* enable NMI/IRQ window open exits if needed */
> - else if (vcpu->arch.nmi_pending)
> - kvm_x86_ops->enable_nmi_window(vcpu);
> - else if (kvm_cpu_has_injectable_intr(vcpu) || req_int_win)
> - kvm_x86_ops->enable_irq_window(vcpu);
> + else {
> + if (vcpu->arch.nmi_pending)
> + kvm_x86_ops->enable_nmi_window(vcpu);
> + if (kvm_cpu_has_injectable_intr(vcpu) || req_int_win)
> + kvm_x86_ops->enable_irq_window(vcpu);
> + }
>
> if (kvm_lapic_enabled(vcpu)) {
> update_cr8_intercept(vcpu);
>
Thanks, queued for 4.6 and stable.
Paolo
prev parent reply other threads:[~2016-03-24 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 5:17 [PATCH v3] KVM: x86: Inject pending interrupt even if pending nmi exist Yuki Shibuya
2016-03-24 11:14 ` 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=56F3CC16.4000608@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=rkrcmar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.