From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/6] KVM: arm/arm64: Do not inject spurious interrupts
Date: Tue, 20 Oct 2015 18:19:02 +0200 [thread overview]
Message-ID: <1445357947-6022-2-git-send-email-christoffer.dall@linaro.org> (raw)
In-Reply-To: <1445357947-6022-1-git-send-email-christoffer.dall@linaro.org>
From: Pavel Fedin <p.fedin@samsung.com>
When lowering a level-triggered line from userspace, we forgot to lower
the pending bit on the emulated CPU interface and we also did not
re-compute the pending_on_cpu bitmap for the CPU affected by the change.
Update vgic_update_irq_pending() to fix the two issues above and also
raise a warning in vgic_quue_irq_to_lr if we encounter an interrupt
pending on a CPU which is neither marked active nor pending.
[ Commit text reworked completely - Christoffer ]
Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
---
virt/kvm/arm/vgic.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
index 6bd1c9b..596455a 100644
--- a/virt/kvm/arm/vgic.c
+++ b/virt/kvm/arm/vgic.c
@@ -1132,7 +1132,8 @@ static void vgic_queue_irq_to_lr(struct kvm_vcpu *vcpu, int irq,
kvm_debug("Set active, clear distributor: 0x%x\n", vlr.state);
vgic_irq_clear_active(vcpu, irq);
vgic_update_state(vcpu->kvm);
- } else if (vgic_dist_irq_is_pending(vcpu, irq)) {
+ } else {
+ WARN_ON(!vgic_dist_irq_is_pending(vcpu, irq));
vlr.state |= LR_STATE_PENDING;
kvm_debug("Set pending: 0x%x\n", vlr.state);
}
@@ -1607,8 +1608,12 @@ static int vgic_update_irq_pending(struct kvm *kvm, int cpuid,
} else {
if (level_triggered) {
vgic_dist_irq_clear_level(vcpu, irq_num);
- if (!vgic_dist_irq_soft_pend(vcpu, irq_num))
+ if (!vgic_dist_irq_soft_pend(vcpu, irq_num)) {
vgic_dist_irq_clear_pending(vcpu, irq_num);
+ vgic_cpu_irq_clear(vcpu, irq_num);
+ if (!compute_pending_for_cpu(vcpu))
+ clear_bit(cpuid, dist->irq_pending_on_cpu);
+ }
}
ret = false;
--
2.1.2.330.g565301e.dirty
next prev parent reply other threads:[~2015-10-20 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 16:19 [GIT PULL 0/6] A handful of fixes for KVM/ARM for v4.3-rc7 Christoffer Dall
2015-10-20 16:19 ` Christoffer Dall [this message]
2015-10-20 16:19 ` [GIT PULL 2/6] KVM: arm/arm64: Fix memory leak if timer initialization fails Christoffer Dall
2015-10-20 16:19 ` [GIT PULL 3/6] KVM: arm: use GIC support unconditionally Christoffer Dall
[not found] ` <672714208.55851501.1445370665940.JavaMail.zimbra@zmail13.collab.prod.int.phx2.redhat.com>
2015-10-21 13:20 ` Christoffer Dall
2015-10-21 13:45 ` Arnd Bergmann
2015-10-21 13:58 ` Christoffer Dall
2015-10-21 14:15 ` Arnd Bergmann
2015-10-21 14:50 ` Pavel Fedin
2015-10-20 16:19 ` [GIT PULL 4/6] arm/arm64: KVM: Fix arch timer behavior for disabled interrupts Christoffer Dall
2015-10-20 16:19 ` [GIT PULL 5/6] arm/arm64: KVM: Clear map->active on pend/active clear Christoffer Dall
2015-10-20 16:19 ` [GIT PULL 6/6] arm/arm64: KVM: Fix disabled distributor operation Christoffer Dall
2015-10-21 15:47 ` [GIT PULL 0/6] A handful of fixes for KVM/ARM for v4.3-rc7 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=1445357947-6022-2-git-send-email-christoffer.dall@linaro.org \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).