From: Matt Gingell <gingell@google.com>
To: kvm@vger.kernel.org
Cc: Steve Rutherford <srutherford@google.com>
Subject: [PATCH 3/3] KVM: x86: fix ready_for_interrupt reporting in split IRQ chip case
Date: Thu, 12 Nov 2015 11:07:56 -0800 [thread overview]
Message-ID: <C9011C2F-D76D-4181-AFDA-41F78ECF7559@google.com> (raw)
This patch adds a call to kvm_arch_interrupt_allowed to ensure ready for
interrupt is reported to user space correctly. This addresses a problem
observed in QEMU when kvm->ready_for_interrupt is set but the x86
interrupt flag is clear.
Additionally, test that the APIC is ready to accept an interrupt before
reporting we are ready for injection.
Reviewed-by: Andy Honig <ahonig@google.com>
Signed-off-by: Matt Gingell <gingell@google.com>
---
arch/x86/kvm/x86.c | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index fd64dee..962003b 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -5835,15 +5835,13 @@ static void post_kvm_run_save(struct kvm_vcpu *vcpu)
kvm_run->flags = is_smm(vcpu) ? KVM_RUN_X86_SMM : 0;
kvm_run->cr8 = kvm_get_cr8(vcpu);
kvm_run->apic_base = kvm_get_apic_base(vcpu);
- if (!irqchip_in_kernel(vcpu->kvm))
+ if (!pic_in_kernel(vcpu->kvm))
kvm_run->ready_for_interrupt_injection =
kvm_arch_interrupt_allowed(vcpu) &&
!kvm_cpu_has_interrupt(vcpu) &&
- !kvm_event_needs_reinjection(vcpu);
- else if (!pic_in_kernel(vcpu->kvm))
- kvm_run->ready_for_interrupt_injection =
- kvm_apic_accept_pic_intr(vcpu) &&
- !kvm_cpu_has_interrupt(vcpu);
+ !kvm_event_needs_reinjection(vcpu) &&
+ (!lapic_in_kernel(vcpu) ||
+ kvm_apic_accept_pic_intr(vcpu));
else
kvm_run->ready_for_interrupt_injection = 1;
}
--
2.6.0.rc2.230.g3dd15c0
next reply other threads:[~2015-11-12 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 19:07 Matt Gingell [this message]
2015-11-13 8:52 ` [PATCH 3/3] KVM: x86: fix ready_for_interrupt reporting in split IRQ chip case Paolo Bonzini
2015-11-13 22:16 ` Steve Rutherford
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=C9011C2F-D76D-4181-AFDA-41F78ECF7559@google.com \
--to=gingell@google.com \
--cc=kvm@vger.kernel.org \
--cc=srutherford@google.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