Messages in this thread | | | From | Dmitry Torokhov <> | Subject | Re: PATCH: 2.6.10 - Misrouted IRQ recovery for review | Date | Tue, 28 Dec 2004 12:28:27 -0500 |
| |
On Tuesday 28 December 2004 12:11 pm, Arjan van de Ven wrote: > On Tue, 2004-12-28 at 15:58 +0000, Alan Cox wrote: > > Ported to the new kernel/irq code. > > > one question; I see you start passing a struct pt_regs around all over > the place; does *anything* actually use that animal, or should we > consider just passing a NULL ..... > (and eventually in 2.7 remove the parameter entirely from irq handlers?) >
From what I saw the only thing that presently uses pt_rergs is SysRq handler to print the call trace and if we slightly change the semantics (instead of printing the trace immediately raise a flag and when next interrupt arrives check it in do_IRQ and print the trace from there - I even had some patches) we could drop pt_regs. I would very much like to do so at least for input drivers.
-- Dmitry - 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/
| |