Re: Shared interrupt (lack of) handling

Alan Cox (alan@lxorguk.ukuu.org.uk)
Thu, 2 Sep 1999 18:25:50 +0100 (BST)


> Wouldn't it be clearer if request_irq() took a function pointer
> to be used to determine whether the interrupt belongs to the
> driver or not? i.e.:

Now I make two expensive indirect jumps per irq.

> At least it would force driver writers to address the shared interrupt
> issue, and if the kernel determines that nobody claims the interrupt
> it could do something about it, like complain, which it can't do at
> the moment. Something that has caused me endless problems on a laptop
> with some unidentifiable PCI device generating unhandled interrupts.

Drivers that don't do proper checking get noticed quite fast - as you've
discovered.

-
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/