Messages in this thread | | | Subject | Re: [patch] irq: do not mask interrupts by default | From | Arjan van de Ven <> | Date | Tue, 14 Nov 2006 09:20:23 +0100 |
| |
> so my patch changes the default irq-disable logic of /all/ controllers > to "delayed disable". (IRQ chips can still override this by providing a > different chip->disable method that just clones their ->mask method, if > it is absolutely sure that no IRQs can be lost while masked) > > So this patch has the worst-case effect of getting at most one 'extra' > interrupt after the IRQ line has been 'disabled' - at which point the > line will be masked for real (by the flow handler). (I updated the > fasteoi and the simple irq flow handlers to mask the IRQ for real if an > IRQ triggers and the line was disabled.)
since disable_irq() is used as locking against interrupt context by several drivers (*cough* ne2000 *cough*) I am not entirely convinced this is a good idea....
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |