From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Neil Brown <neilb@suse.de>
Subject: Re: [PATCH 2.6.16] Shared interrupts sometimes lost
Date: Sat, 08 Apr 2006 08:10:38 -0600 [thread overview]
Message-ID: <4437C45E.8010503@shaw.ca> (raw)
In-Reply-To: <5Zd5E-3vi-7@gated-at.bofh.it>
Neil Brown wrote:
> However there is room for a race here. If an event occurs between
> the read and the write, then this will NOT de-assert the IRQ line.
> It will remain asserted throughout.
>
> Now if the IRQ is handled as an edge-triggered line (which I believe
> they are in Linux), then losing this race will mean that we don't see
> any more interrupts on this line.
PCI interrupts should always be level triggered, not edge triggered
(except maybe in a few special cases - non-native-mode PCI IDE maybe?
and in those cases I don't think the interrupt is considered sharable).
With a level triggered interrupt the ISR will simply be triggered again
and the event handled in this case so there is no race. I think this
patch is going to double interrupt overhead and only covers up some
other problem.
I think that in cases where the interrupt is edge triggered and is
shared (for example on ISA cards that support it) the kernel already has
such logic as you describe.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-04-08 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5Zd5E-3vi-7@gated-at.bofh.it>
2006-04-08 14:10 ` Robert Hancock [this message]
2006-04-09 9:48 ` How to correct ELCR? - was Re: [PATCH 2.6.16] Shared interrupts sometimes lost Neil Brown
2006-04-09 15:48 ` Francois Romieu
2006-04-09 22:28 ` Neil Brown
2006-04-11 17:07 ` Pavel Machek
2006-04-12 4:01 ` Neil Brown
[not found] ` <5ZoDL-3rE-7@gated-at.bofh.it>
2006-04-09 18:12 ` Robert Hancock
2006-04-09 18:24 ` Lee Revell
2006-04-08 4:10 Neil Brown
2006-04-08 16:31 ` Lee Revell
2006-04-09 6:02 ` Neil Brown
2006-04-11 17:07 ` Pavel Machek
2006-04-12 0:01 ` Neil Brown
2006-04-13 5:41 ` Pavel Machek
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=4437C45E.8010503@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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).