--- Quote Start ---
originally posted by jskjoet@Dec 3 2005, 09:42 PM
_interrupt_handler enables interrupts after the isr has been called but before posting the dsr (the comments wrongly states that the dsr is called - but it is just added to the list - right ? ).
if we have an interrupt storm this means that each interrupt takes up app 76 bytes on the stack of the thread being interrupted - this might pose a problem.
why not wait and let the eret instruction reenable ints - to prevent eating stack in case of an interrupt storm ? --- Quote End ---
Correct me if I'm wrong, but isn't this why the ISR masks its interrupt and the DSR unmasks it? If that same interrupt comes in between ISR and DSR, it has to wait for unmasking, at which point the DSR should be mostly done.