From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL 8/8] KVM: arm/arm64: vgic-new: Removel harmful BUG_ON
Date: Thu, 2 Jun 2016 12:21:00 +0200 [thread overview]
Message-ID: <1464862860-1183-9-git-send-email-christoffer.dall@linaro.org> (raw)
In-Reply-To: <1464862860-1183-1-git-send-email-christoffer.dall@linaro.org>
From: Marc Zyngier <marc.zyngier@arm.com>
When changing the active bit from an MMIO trap, we decide to
explode if the intid is that of a private interrupt.
This flawed logic comes from the fact that we were assuming that
kvm_vcpu_kick() as called by kvm_arm_halt_vcpu() would not return before
the called vcpu responded, but this is not the case, so we need to
perform this wait even for private interrupts.
Dropping the BUG_ON seems like the right thing to do.
[ Commit message tweaked by Christoffer ]
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
---
virt/kvm/arm/vgic/vgic-mmio.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/virt/kvm/arm/vgic/vgic-mmio.c b/virt/kvm/arm/vgic/vgic-mmio.c
index 059595e..9f6fab7 100644
--- a/virt/kvm/arm/vgic/vgic-mmio.c
+++ b/virt/kvm/arm/vgic/vgic-mmio.c
@@ -191,10 +191,8 @@ static void vgic_mmio_change_active(struct kvm_vcpu *vcpu, struct vgic_irq *irq,
* other thread sync back the IRQ.
*/
while (irq->vcpu && /* IRQ may have state in an LR somewhere */
- irq->vcpu->cpu != -1) { /* VCPU thread is running */
- BUG_ON(irq->intid < VGIC_NR_PRIVATE_IRQS);
+ irq->vcpu->cpu != -1) /* VCPU thread is running */
cond_resched_lock(&irq->irq_lock);
- }
irq->active = new_active_state;
if (new_active_state)
--
2.1.2.330.g565301e.dirty
next prev parent reply other threads:[~2016-06-02 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 10:20 [PULL 0/8] KVM/ARM Fixes for v4.7-rc2 Christoffer Dall
2016-06-02 10:20 ` [PULL 1/8] KVM: arm/arm64: vgic-v2: Clear all dirty LRs Christoffer Dall
2016-06-02 10:20 ` [PULL 2/8] KVM: arm/arm64: vgic-v3: " Christoffer Dall
2016-06-02 10:20 ` [PULL 3/8] KVM: arm/arm64: vgic-v2: Always resample level interrupts Christoffer Dall
2016-06-02 10:20 ` [PULL 4/8] KVM: arm/arm64: vgic-v3: " Christoffer Dall
2016-06-02 10:20 ` [PULL 5/8] arm64: KVM: Make ICC_SRE_EL1 access return the configured SRE value Christoffer Dall
2016-06-02 10:20 ` [PULL 6/8] arm64: KVM: vgic-v3: Prevent the guest from messing with ICC_SRE_EL1 Christoffer Dall
2016-06-02 10:20 ` [PULL 7/8] arm64: KVM: vgic-v3: Relax synchronization when SRE==1 Christoffer Dall
2016-06-02 10:21 ` Christoffer Dall [this message]
2016-06-02 13:52 ` [PULL 0/8] KVM/ARM Fixes for v4.7-rc2 Radim Krčmář
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=1464862860-1183-9-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).