The idea of Chained IRQ Handlers

XCHG · Post by **XCHG** » Fri Mar 23, 2007 3:19 am

I recently coded some procedures in my kernel that allow individual procedures to register themselves as Extra IRQ Handlers. So for example IRQ 3 can be handled by more than 1 procedure which is the actual IRQ3 handler. I was wondering if this might bring the system down later or whether it is a good or a bad idea. I needed it so I designed it. I don't know if there are other ways around this problem so I'd appreciate it if you could share your thoughts on this matter.

Combuster · Post by **Combuster** » Fri Mar 23, 2007 4:27 am

If you have shared IRQs, the common approach is to have one driver hooked up to it, which in turn invoked all the (neccessary) handlers.

XCHG · Post by **XCHG** » Fri Mar 23, 2007 5:00 am

Right now I have at least one procedure for each IRQ that handles the IRQs. Each of those procedures can allow the chained procedures to be executed or not. So there is at least one handler per IRQ. That must be advantageous for handling shared IRQs right?