From: "La Monte H.P. Yarroll" <piggy@timesys.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Scott Wood <scott@timesys.com>,
Andrey Panin <pazke@donpac.ru>
Subject: Re: [patch] generic-hardirqs.patch, 2.6.9-rc1-bk14
Date: Wed, 08 Sep 2004 08:29:05 -0400 [thread overview]
Message-ID: <413EFB11.2000507@timesys.com> (raw)
In-Reply-To: <20040908120613.GA16916@elte.hu>
Ingo Molnar wrote:
>the attached patch moves generic hardirq handling bits to
>kernel/hardirq.c. It is not a replacement for any of the existing IRQ
>functions, so architectures can use their existing hardirq code in an
>unmodified form. It is a library of generic functions that an
>architecture can make use of optionally.
>
>I've fully converted x86's irq.c to use the new functions, and Scott
>Wood has done the same for ppc/ppc64 as well. (the arch-ppc* changes are
>not included in this patch because i couldnt test them myself in the
>current port of this patch - but the generic bits were tested on ppc.)
>
>
In the interests of full provinence, the TimeSys patches are based on
work by Andrey Panin.
>i have test-compiled and test-booted the patch on x86 and x64, on SMP &&
>PREEMPT and !SMP && !PREEMPT kernels. x64 needed only a single change (a
>setup_irq() prototype) to work fine, which makes me believe that the
>patch will not break other architectures either.
>
>(a more complex version of this patch has been tested for weeks as part
>of the voluntary-preempt patches as well.)
>
> Ingo
>
>
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell's sig
next prev parent reply other threads:[~2004-09-08 12:29 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 [this message]
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
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=413EFB11.2000507@timesys.com \
--to=piggy@timesys.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pazke@donpac.ru \
--cc=scott@timesys.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