|| ||Andi Kleen <andi-AT-firstfloor.org>|
|| ||Thomas Gleixner <tglx-AT-linutronix.de>|
|| ||Re: [RFC patch 0/5] genirq: add infrastructure for threaded interrupt handlers|
|| ||Thu, 02 Oct 2008 16:46:09 +0200|
|| ||LKML <linux-kernel-AT-vger.kernel.org>,
Linus Torvalds <torvalds-AT-osdl.org>,
Andrew Morton <akpm-AT-linux-foundation.org>,
Ingo Molnar <mingo-AT-elte.hu>,
Arjan van de Veen <arjan-AT-infradead.org>,
Benjamin Herrenschmidt <benh-AT-kernel.crashing.org>,
Steven Rostedt <rostedt-AT-goodmis.org>,
Jon Masters <jonathan-AT-jonmasters.org>,
Sven Dietrich <sdietrich-AT-suse.de>|
Thomas Gleixner <firstname.lastname@example.org> writes:
> - move long running handlers out of the hard interrupt context
I'm not sure I'm really looking forward to this brave new world
of very long running interrupt handlers. e.g. what do you
do for example when some handler blocks for a very long time?
> - improved debugability of the kernel: faulty handlers do not take
> down the system.
I had an old patch to handle this without threaded interrupts.
What normally happens is when a interrupt oopses it tries to kill the
idle process which panics. My fix was to just restart another idle
process instead of panicing.
But back then it was rejected by Linus with the argument that
a crashing interrupt handler will typically hold some lock
and the next time the interrupt happens it will deadlock on that
Has that changed with your threaded interrupts?
If it has changed I suspect the restart idle change could
be made to work to be equivalent in debuggability.
> Comments, reviews, flames as usual.
To be honest my opinion is that it will encourage badly written interrupt
code longer term.
to post comments)