Development Plan Proposal for Unifying Interrupt and PCI APIs

gregory.menke at gregory.menke at
Sun Oct 24 21:39:19 UTC 2004

Leon Pollak writes:
 > On Sunday 24 October 2004 12:58, Pavel Pisa wrote:
 > > is received. Only correct solution is to call all members of chain
 > > again and again until one full round is not returning no interrupt
 > > serviced state.
 > ....and an interrupt fires exactly at the moment when A returned "no interrupt 
 > serviced"...:-)

The default Mongoose bsp vectoring code takes this approach, mostly
because its cheaper to service a bunch of interrupts than to unwind
the interrupt service routine, then enter it again.  It sort of
preserves the concept of interrupt priority by scanning the interrupt
causes in defined if arbitrary priority order.


More information about the users mailing list