From: Alexander Graf <agraf@suse.de>
To: kwolf@redhat.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH] AHCI: Masking of IRQs actually masks them
Date: Mon, 30 Jan 2012 23:29:48 +0100 [thread overview]
Message-ID: <1327962588-5230-3-git-send-email-agraf@suse.de> (raw)
In-Reply-To: <1327962588-5230-1-git-send-email-agraf@suse.de>
When masking IRQ lines, we should actually mask them out and not declare
them active anymore. Once we mask them in again, they are allowed to trigger
again.
Signed-off-by: Alexander Graf <agraf@suse.de>
---
hw/ide/ahci.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/hw/ide/ahci.c b/hw/ide/ahci.c
index c2c168d..f8e9eb4 100644
--- a/hw/ide/ahci.c
+++ b/hw/ide/ahci.c
@@ -146,6 +146,7 @@ static void ahci_check_irq(AHCIState *s)
DPRINTF(-1, "check irq %#x\n", s->control_regs.irqstatus);
+ s->control_regs.irqstatus = 0;
for (i = 0; i < s->ports; i++) {
AHCIPortRegs *pr = &s->dev[i].port_regs;
if (pr->irq_stat & pr->irq_mask) {
@@ -216,6 +217,7 @@ static void ahci_port_write(AHCIState *s, int port, int offset, uint32_t val)
break;
case PORT_IRQ_STAT:
pr->irq_stat &= ~val;
+ ahci_check_irq(s);
break;
case PORT_IRQ_MASK:
pr->irq_mask = val & 0xfdc000ff;
--
1.6.0.2
next prev parent reply other threads:[~2012-01-30 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 22:29 [Qemu-devel] [PATCH] ATA: Allow WIN_SECURITY_FREEZE_LOCK as nop Alexander Graf
2012-01-30 22:29 ` [Qemu-devel] [PATCH] AHCI: Fix port reset race Alexander Graf
2012-02-09 14:42 ` Kevin Wolf
2012-01-30 22:29 ` Alexander Graf [this message]
2012-02-09 14:41 ` [Qemu-devel] [PATCH] AHCI: Masking of IRQs actually masks them Kevin Wolf
2012-02-09 14:52 ` Alexander Graf
2012-02-07 14:57 ` [Qemu-devel] [PATCH] ATA: Allow WIN_SECURITY_FREEZE_LOCK as nop Andreas Färber
2012-02-07 15:01 ` Alexander Graf
2012-02-09 14:28 ` Kevin Wolf
2012-02-09 14:49 ` Alexander Graf
2012-02-09 14:59 ` Kevin Wolf
2012-02-09 15:01 ` Alexander Graf
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=1327962588-5230-3-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=jan.kiszka@siemens.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.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).