From: Arjan van de Ven <arjanv@redhat.com>
To: 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, Scott Wood <scott@timesys.com>
Subject: Re: [patch] generic-hardirqs-2.6.9-rc1-mm4.patch
Date: Thu, 9 Sep 2004 19:54:41 +0200 [thread overview]
Message-ID: <20040909175441.GA25686@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040909175314.GD3106@holomorphy.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Thu, Sep 09, 2004 at 10:53:14AM -0700, William Lee Irwin III wrote:
> On Thu, Sep 09, 2004 at 07:24:01PM +0200, Ingo Molnar wrote:
> > you can find a pretty good approximation done by Scott Wood (and Andrey
> > Panin?) in the ppc/ppc64 portion of the VP patches:
> > http://redhat.com/~mingo/voluntary-preempt/voluntary-preempt-2.6.9-rc1-bk12-S0
> > basically you only have to zap some of the irq-threading changes such as
> > calls to redirect_hardirq(), do a s/generic_// and zap the PIC changes
> > (these are done for redirection too). Scott has tested those changes so
> > kernel/hardirq.c should work pretty well with ppc/ppc64.
>
> By any chance can the generic code be made not to be reliant on
> irq_desc[] and/or irq_desc[] being an array?
I would say one step at a time.
First extract out the code that most arch's share already
only THEN start working on seeing if the few remaining ones can be moved in,
and if other cleanups are appropriate
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-09 18:00 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 [this message]
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
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=20040909175441.GA25686@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--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