Hi Felipe, On Thu, 12 Mar 2009, Felipe Balbi wrote: > This is the link where Ingo discusses why !IRQF_DISABLED could cause > stack overflow: > > http://lkml.org/lkml/2009/3/3/71 > > You probably wanna take a look at the whole thread to figure out the > discussion, but basically Ingo and Peter (Zijlstra) believe > !IRQF_DISABLED is a bug and drivers needing that probably should be > using threaded irqs (which is not yet merged) or the hw is broken, and > for those an IRQF_ENABLED flag will be created and a TAINT will also be > placed. > > Once that gets merged, all drivers will be forced (at some point) to > IRQF_DISABLED and those which don't want that will be moved gradually to > threaded irq. > > This patch is also interesting: > > http://lkml.org/lkml/2009/3/2/33 Thanks for the links. Those issues are indeed distinct from the spurious IRQ problem that Ari is reporting. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
