From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Arjan van de Ven <arjan@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
mingo@redhat.com
Subject: Re: PATCH: 2.6.10 - Misrouted IRQ recovery for review
Date: Tue, 28 Dec 2004 12:28:27 -0500 [thread overview]
Message-ID: <200412281228.27307.dtor_core@ameritech.net> (raw)
In-Reply-To: <1104253919.4173.11.camel@laptopd505.fenrus.org>
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
next prev parent reply other threads:[~2004-12-28 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 15:58 PATCH: 2.6.10 - Misrouted IRQ recovery for review Alan Cox
2004-12-28 17:11 ` Arjan van de Ven
2004-12-28 16:37 ` Alan Cox
2004-12-28 17:28 ` Dmitry Torokhov [this message]
2004-12-28 18:25 ` David S. Miller
2004-12-28 18:50 ` Dmitry Torokhov
2004-12-28 18:53 ` David S. Miller
2004-12-28 19:21 ` Dmitry Torokhov
2004-12-28 19:26 ` David S. Miller
2004-12-29 13:57 ` Ingo Molnar
2005-01-01 17:59 ` Pavel Machek
2005-01-01 20:41 ` Bill Davidsen
2005-01-02 15:18 ` Alan Cox
2005-01-02 17:47 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412281228.27307.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox