On Wed, 26 Jul 2000, Tigran Aivazian wrote:
>
> On Wed, 26 Jul 2000, Linus Torvalds wrote:
> > We use the interrupt blocking hardware to make sure that as long
> > as irq A is running, further instances of irq A are blocked. OTHER
> > interrupts can still happen.
>
> I thought this depended on whether SA_INTERRUPT is passed or is this not
> the case anymore (it was the case in 2.2.x). I.e.
SA_INTERRUPT is deprecated, as it fundamentally cannot work with shared
interrupts (or at least they all have to _agree_ on SA_INTERRUPT, which
basically means that you have to know exactly the type of sharing. Ugh).
And non-shared interrupts are _definitely_ deprecated, unless the hardware
really forces you to use them. That kind of hardware is getting quite
rare. Thank God.
That said, SA_INTERRUPT still works, but it's really only meant to be used
for the timer handler (you don't want the timer to be interruptible: it's
fast, and at least the SCSI layer historically wanted the timer to tick
_while_ a SCSI interrupt is active, so you must not have a SCSI interrupt
interrupt the timer, because if that happens..)
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:22 EST