From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Scott Wood <scott@timesys.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
William Lee Irwin III <wli@holomorphy.com>,
Ingo Molnar <mingo@elte.hu>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] generic-hardirqs-2.6.9-rc1-mm4.patch
Date: Thu, 9 Sep 2004 22:00:04 +0100 [thread overview]
Message-ID: <20040909220004.F6434@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040909205153.GA1014@yoda.timesys>; from scott@timesys.com on Thu, Sep 09, 2004 at 04:51:53PM -0400
On Thu, Sep 09, 2004 at 04:51:53PM -0400, Scott Wood wrote:
> On Thu, Sep 09, 2004 at 09:10:38PM +0100, Russell King wrote:
> > If it uses irq_desc then ARM won't use it. irq_desc is part of the
> > far-too-restrictive x86 IRQ handlign code which is unsuitable for
> > ARM platforms.
>
> What does ARM need that irq_desc doesn't provide, and which could not
> be added? IMHO, it'd be better to fix the generic code than maintain
> completely separate implementations.
Unfortunately, to deal with this issue would mean breaking off from
planned work, so I'm not going to be in a position to do an element
by element comparison of the structures for some time.
Maybe I can look at it after the weekend though.
However, I think if you just compare:
linux/include/linux/irq.h
linux/include/asm-arm/mach/irq.h
you'll realise how inadequate the "generic" IRQ code is for ARM.
Note that IRQ handling on ARM is a multi-level affair where we have
multiple levels of interrupt controllers which need to be traversed
in software.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-09-09 21:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 12:06 [patch] generic-hardirqs.patch, 2.6.9-rc1-bk14 Ingo Molnar
2004-09-08 12:29 ` La Monte H.P. Yarroll
2004-09-08 13:25 ` Christoph Hellwig
2004-09-08 13:40 ` Ingo Molnar
2004-09-08 13:47 ` Christoph Hellwig
2004-09-08 12:34 ` Christoph Hellwig
2004-09-08 12:45 ` Ingo Molnar
2004-09-08 12:49 ` Christoph Hellwig
2004-09-08 13:05 ` Ingo Molnar
2004-09-08 13:12 ` Christoph Hellwig
2004-09-08 13:17 ` Ingo Molnar
2004-09-08 13:20 ` Christoph Hellwig
2004-09-08 13:32 ` Ingo Molnar
2004-09-09 17:56 ` Scott Wood
2004-09-08 12:57 ` William Lee Irwin III
2004-09-08 13:01 ` Christoph Hellwig
2004-09-08 13:09 ` William Lee Irwin III
2004-09-08 13:10 ` Ingo Molnar
2004-09-08 13:34 ` Zwane Mwaikambo
2004-09-08 13:31 ` Christoph Hellwig
2004-09-08 13:47 ` Zwane Mwaikambo
2004-09-08 14:09 ` Arjan van de Ven
2004-09-08 18:25 ` Ingo Molnar
2004-09-08 18:42 ` Zwane Mwaikambo
2004-09-08 21:14 ` [patch] generic-hardirqs-2.6.9-rc1-mm4.patch Ingo Molnar
2004-09-09 16:57 ` Christoph Hellwig
2004-09-09 17:24 ` Ingo Molnar
2004-09-09 17:53 ` William Lee Irwin III
2004-09-09 17:54 ` Arjan van de Ven
2004-09-09 17:56 ` William Lee Irwin III
2004-09-09 20:10 ` Russell King
2004-09-09 20:51 ` Scott Wood
2004-09-09 21:00 ` Russell King [this message]
2004-09-10 5:57 ` Arjan van de Ven
2004-09-09 20:24 ` Rafael J. Wysocki
2004-09-09 20:40 ` Andrew Morton
2004-09-09 20:49 ` Ingo Molnar
2004-09-08 13:03 ` [patch] generic-hardirqs.patch, 2.6.9-rc1-bk14 Arjan van de Ven
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=20040909220004.F6434@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=scott@timesys.com \
--cc=wli@holomorphy.com \
--cc=zwane@linuxpower.ca \
/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