From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstraem-fixes] ata_piix: detect and clear spurious IRQs
Date: Wed, 26 Nov 2008 11:45:32 +0900 [thread overview]
Message-ID: <492CB84C.8090706@kernel.org> (raw)
In-Reply-To: <20081125171559.222e499f@lxorguk.ukuu.org.uk>
Alan Cox wrote:
> On Tue, 25 Nov 2008 12:08:12 -0500
> Jeff Garzik <jeff@garzik.org> wrote:
>
>> Tejun Heo wrote:
>>> The DMA_IRQ bit in the bmdma status register is always set when IDEIRQ
>>> is asserted allowing spurious IRQ detection. Detect spurious IRQs and
>>> clear them. This protects ata_piix against nobody-cared which gets
>>> reported not so rarely.
>>>
>>> Signed-off-by: Tejun Heo <tj@kernel.org>
>>> ---
>>> drivers/ata/ata_piix.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++-
>>> 1 file changed, 53 insertions(+), 1 deletion(-)
>> It's tough to call this #upstream-fixes material, unfortunately... For
>> this late into -rc, I am very nervous about changing the ATA interrupt
>> path for millions of machines.
>
> I would like to go through the PIIX errata first. There are some rules
> about what registers may not be touched during a transfer on some of the
> devices and breaking them is *bad*. I don't think this is a problem but
> it makes me nervous.
Well, the BMDMA status register read and cleared iff no qc is in
flight so the patch isn't likely to break any of that. That said,
it's true that this is a big change this late in the release cycle. I
have no problem with postponing it to the next -rc1. Also, this patch
is already in openSUSE11.1 and SLES11 betas, so we'll know a lot more
about how this works in the coming weeks. :-)
Thanks.
--
tejun
next prev parent reply other threads:[~2008-11-26 2:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 4:13 [PATCH #upstraem-fixes] ata_piix: detect and clear spurious IRQs Tejun Heo
2008-11-21 10:25 ` Alan Cox
2008-11-21 13:07 ` Tejun Heo
2008-11-25 17:07 ` Jeff Garzik
2008-11-26 2:52 ` Tejun Heo
2008-11-26 10:47 ` Alan Cox
2008-11-26 12:26 ` Sergei Shtylyov
2008-11-26 12:28 ` Sergei Shtylyov
2008-11-26 12:37 ` Sergei Shtylyov
2008-11-26 17:34 ` Jeff Garzik
2008-11-26 17:45 ` Tejun Heo
2008-11-26 18:40 ` Alan Cox
2008-11-26 18:57 ` Tejun Heo
2008-11-28 2:31 ` Tejun Heo
2008-12-04 16:33 ` Mark Lord
2008-12-04 16:35 ` Alan Cox
2008-11-21 16:59 ` Sergei Shtylyov
2008-11-21 17:05 ` Tejun Heo
2008-11-25 17:08 ` Jeff Garzik
2008-11-25 17:15 ` Alan Cox
2008-11-26 2:45 ` Tejun Heo [this message]
2008-11-26 10:33 ` Alan Cox
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=492CB84C.8090706@kernel.org \
--to=tj@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.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).