From: "H. Peter Anvin" <hpa@zytor.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: x86@kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] irq: handle irq0 special only on x86
Date: Tue, 12 Jan 2010 20:59:21 -0800 [thread overview]
Message-ID: <4B4D5329.7050107@zytor.com> (raw)
In-Reply-To: <20100112155929.GA5615@pengutronix.de>
On 01/12/2010 07:59 AM, Uwe Kleine-König wrote:
> the feed-back I have got up to now wasn't helpfull. (Only some "irq0 is
> evil---no it's not" discussion.) So what do you think? I admit the
> #ifdef isn't nice, but if the semantic is OK I'm willing to rework it
> into something more pretty.
There was a debate on this a long time ago, and the outcome was that IRQ
0 is invalid, across the kernel, and that it is up to each architecture
to carry exceptions (like IRQ 0 for the timer interrupt in x86.) Hinc
dictat Linus, so you would have to convince him before any of the arch
maintainer could realistically even consider this change.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
prev parent reply other threads:[~2010-01-13 5:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 9:20 [PATCH] irq: handle irq0 special only on x86 Uwe Kleine-König
2009-12-09 9:28 ` Américo Wang
2009-12-09 9:35 ` Uwe Kleine-König
2009-12-09 9:41 ` David Miller
2009-12-10 8:24 ` Uwe Kleine-König
2009-12-10 16:40 ` H. Peter Anvin
2009-12-13 0:34 ` Maciej W. Rozycki
2009-12-16 14:04 ` Uwe Kleine-König
2010-01-12 15:59 ` Uwe Kleine-König
2010-01-13 4:59 ` H. Peter Anvin [this message]
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=4B4D5329.7050107@zytor.com \
--to=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.