On Fri, 15 Jun 2018, Ricardo Neri wrote: > On Fri, Jun 15, 2018 at 09:01:02AM +0100, Julien Thierry wrote: > > In my patches, I'm not sure there is much to adapt to your work as most of > > it is arch specific (although I wont say no to another pair of eyes looking > > at them). From what I've seen of your patches, the point where we converge > > is that need for some code to be able to tell the irqchip "I want that > > particular interrupt line to be treated/setup as an NMI". > > Indeed, there has to be a generic way for the irqchip to announce that it > supports configuring an interrupt as NMI... and a way to actually configuring > it. There has to be nothing. The irqchip infrastructure might be able to provide certain aspects of NMI support, perhaps for initialization, but everything else is fundamentally different and the executional parts simply cannot use any of the irq chip functions at all. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
