> Because running irq handlers with irqs enabled it plain silly. It makes enormous sense to run with the ability to mask *just* the IRQ that occurred and not others so that long lasting interrupts. There is another reason not to do this of course - the real time work makes it essentially irrelevant by doing the job right and reducing the entire problem space to software priority management. > Except it turns out there is some really broken ass hardware out there. > But supposedly IDE PIO could be done from a threaded handler. Only if you support reliable masking of a single IRQ *after* the IRQ handler returns. The real time patches can do that for some chipsets but on the PC at least you are into the realms of deepest darkest APIC weirdness and that requires Ingo's pointy hat and wand.. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
