Patchwork [7/7] ahci: work around bug with level interrupts

login
register
mail settings
Submitter Alexander Graf
Date Feb. 1, 2011, 6:35 p.m.
Message ID <1296585301-15510-1-git-send-email-agraf@suse.de>
Download mbox | patch
Permalink /patch/81349/
State New
Headers show

Comments

Alexander Graf - Feb. 1, 2011, 6:35 p.m.
When using level based interrupts, the interrupt is treated the same as an
edge triggered one: leaving the line up does not retrigger the interrupt.

In fact, when not lowering the line, we won't ever get a new interrupt inside
the guest. So let's always retrigger an interrupt as soon as the OS ack'ed
something on the device. This way we're sure the guest doesn't starve on
interrupts until someone fixes the actual interrupt path.

Signed-off-by: Alexander Graf <agraf@suse.de>

---

v2 -> v3:

  - add comment about the interrupt hack
---
 hw/ide/ahci.c |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)

Patch

diff --git a/hw/ide/ahci.c b/hw/ide/ahci.c
index 98bdf70..95e1cf7 100644
--- a/hw/ide/ahci.c
+++ b/hw/ide/ahci.c
@@ -152,11 +152,15 @@  static void ahci_check_irq(AHCIState *s)
         }
     }
 
+    /* XXX We lower the interrupt line here because of a bug with interrupt
+           handling in Qemu. When leaving a line up, the interrupt does
+           not get retriggered automatically currently. Once that bug is fixed,
+           this workaround is not necessary anymore and we only need to lower
+           in the else branch. */
+    ahci_irq_lower(s, NULL);
     if (s->control_regs.irqstatus &&
         (s->control_regs.ghc & HOST_CTL_IRQ_EN)) {
             ahci_irq_raise(s, NULL);
-    } else {
-        ahci_irq_lower(s, NULL);
     }
 }