From: Jes Sorensen <jes@sunsite.dk>
To: Chris Wedgwood <cw@f00f.org>
Cc: Andrew McNamara <andrewm@connect.com.au>, linux-kernel@vger.kernel.org
Subject: Re: how to tell Linux *not* to share IRQs ?
Date: 07 Aug 2001 17:09:47 +0200 [thread overview]
Message-ID: <d33d73x5xg.fsf@lxplus014.cern.ch> (raw)
In-Reply-To: <20010726070621.D69A1BE91@wawura.off.connect.com.au> <20010726193934.A29055@weta.f00f.org>
In-Reply-To: Chris Wedgwood's message of "Thu, 26 Jul 2001 19:39:34 +1200"
>>>>> "Chris" == Chris Wedgwood <cw@f00f.org> writes:
Chris> On Thu, Jul 26, 2001 at 05:06:21PM +1000, Andrew McNamara
> wrote: Does this mean the ISRs for every driver sharing an
> interrupt have to poll their device when an interrupt comes in
> (in the case of shared PCI interrupts), or is there some
> additional hardware smarts so the kernel knows which driver's
> ISRs need to be invoked?
Chris> Yes, drivers need to check their hardware devices and
Chris> acknowledge whether or not it's was their interrupt or not. It
Chris> sounds terrible but even with many thousands of interrupts per
Chris> second the cost doesn't seem to be that high.
Not only is this the case, it's also the only sane thing to do <tm>,
any device driver should check the status of the hardware it is
serving before doing anything else.
Jes
next prev parent reply other threads:[~2001-08-07 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 23:23 how to tell Linux *not* to share IRQs ? Scott McDermott
2001-07-25 23:37 ` Alan Cox
2001-07-26 7:06 ` Andrew McNamara
2001-07-26 7:39 ` Chris Wedgwood
2001-08-07 15:09 ` Jes Sorensen [this message]
2001-08-08 0:05 ` Andrew McNamara
2001-08-08 11:14 ` Eric W. Biederman
2001-08-08 17:13 ` Mark H. Wood
2001-07-26 7:54 ` Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2001-08-08 19:03 Per Jessen
2001-08-08 19:19 ` Chris Meadors
2001-11-06 23:17 ` H. Peter Anvin
2001-08-09 14:27 ` Andreas Bombe
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=d33d73x5xg.fsf@lxplus014.cern.ch \
--to=jes@sunsite.dk \
--cc=andrewm@connect.com.au \
--cc=cw@f00f.org \
--cc=linux-kernel@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