linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL 4/8] KVM: arm/arm64: vgic-v3: Always resample level interrupts
Date: Thu,  2 Jun 2016 12:20:56 +0200	[thread overview]
Message-ID: <1464862860-1183-5-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 reading back from the list registers, we need to perform
two actions for level interrupts:
1) clear the soft-pending bit if the interrupt is not pending
   anymore *in the list register*
2) resample the line level and propagate it to the pending state

But these two actions shouldn't be linked, and we should *always*
resample the line level, no matter what state is in the list
register. Otherwise, we may end-up injecting spurious interrupts
that have been already retired.

Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
---
 virt/kvm/arm/vgic/vgic-v3.c | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/virt/kvm/arm/vgic/vgic-v3.c b/virt/kvm/arm/vgic/vgic-v3.c
index 336a461..346b4ad 100644
--- a/virt/kvm/arm/vgic/vgic-v3.c
+++ b/virt/kvm/arm/vgic/vgic-v3.c
@@ -101,11 +101,15 @@ void vgic_v3_fold_lr_state(struct kvm_vcpu *vcpu)
 			}
 		}
 
-		/* Clear soft pending state when level irqs have been acked */
-		if (irq->config == VGIC_CONFIG_LEVEL &&
-		    !(val & ICH_LR_PENDING_BIT)) {
-			irq->soft_pending = false;
-			irq->pending = irq->line_level;
+		/*
+		 * Clear soft pending state when level irqs have been acked.
+		 * Always regenerate the pending state.
+		 */
+		if (irq->config == VGIC_CONFIG_LEVEL) {
+			if (!(val & ICH_LR_PENDING_BIT))
+				irq->soft_pending = false;
+
+			irq->pending = irq->line_level || irq->soft_pending;
 		}
 
 		spin_unlock(&irq->irq_lock);
-- 
2.1.2.330.g565301e.dirty

  parent reply	other threads:[~2016-06-02 10:20 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 ` Christoffer Dall [this message]
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 ` [PULL 8/8] KVM: arm/arm64: vgic-new: Removel harmful BUG_ON Christoffer Dall
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-5-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).