From: "David S. Miller" <davem@davemloft.net>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, arjan@infradead.org,
alan@lxorguk.ukuu.org.uk, mingo@redhat.com
Subject: Re: PATCH: 2.6.10 - Misrouted IRQ recovery for review
Date: Tue, 28 Dec 2004 10:53:30 -0800 [thread overview]
Message-ID: <20041228105330.6da0f0ea.davem@davemloft.net> (raw)
In-Reply-To: <200412281350.44195.dtor_core@ameritech.net>
On Tue, 28 Dec 2004 13:50:40 -0500
Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> Please look at the patch below (handful of arches only and against
> some old tree, but you'll see what I wanted to do). What I meant
> by changing the semantics is that reporting is delayed by 1 interrupt.
This looks exactly like what I was looking for. I think I misunderstood
your original description, which is why it is always best to communicate
ideas using patches :)
My misunderstanding what that I thought that your flag would work
like this:
1) input interrupt occurs, flag is set
2) IRQ handling completes
3) some new IRQ arrives, and this is when we test
the flag for dumping sysrq regs
That, fortunately, is not what your patch is doing.
> This is for only one IRQ handler I believe which I think we can
> do special-case for. Is it for math-emulation only?
I rather believe it is for vm86 IRQ handling.
next prev parent reply other threads:[~2004-12-28 18:55 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
2004-12-28 18:25 ` David S. Miller
2004-12-28 18:50 ` Dmitry Torokhov
2004-12-28 18:53 ` David S. Miller [this message]
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=20041228105330.6da0f0ea.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=dtor_core@ameritech.net \
--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