From: Lee Revell <rlrevell@joe-job.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.16] Shared interrupts sometimes lost
Date: Sat, 08 Apr 2006 12:31:36 -0400 [thread overview]
Message-ID: <1144513897.22490.154.camel@mindpipe> (raw)
In-Reply-To: <17463.14285.31029.943738@cse.unsw.edu.au>
On Sat, 2006-04-08 at 14:10 +1000, Neil Brown wrote:
>
> To explain what I think is happening, let me start with a very simple
> case. A number of PCI devices (this one included) have a number of
> events which can trigger an interrupt. The events which are current
> are presented as bits in a register, and are ORed together (and
> possibly masked by another register) to make the IRQ line.
> When 1's are written to any bits in this register, it acknowledges
> the event and clears the bit.
> A typical code fragment is
> events = read_register(INTERRUPTS);
> write_register(INTERRUPTS, events);
> ... handle each 1 bits in events ....
>
Isn't a more typical IRQ handler:
while (events = read_register(INTERRUPTS) != 0) {
...handle each bit in events and ACK it...
}
Lee
next prev parent reply other threads:[~2006-04-08 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 4:10 [PATCH 2.6.16] Shared interrupts sometimes lost Neil Brown
2006-04-08 16:31 ` Lee Revell [this message]
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
[not found] <5Zd5E-3vi-7@gated-at.bofh.it>
2006-04-08 14:10 ` Robert Hancock
[not found] ` <5ZoDL-3rE-7@gated-at.bofh.it>
2006-04-09 18:12 ` Robert Hancock
2006-04-09 18:24 ` Lee Revell
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=1144513897.22490.154.camel@mindpipe \
--to=rlrevell@joe-job.com \
--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