public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Anton Blanchard <anton@samba.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] disable_irq()/enable_irq() semantics and ide-probe.c
Date: Fri, 17 Oct 2003 12:32:16 +0200	[thread overview]
Message-ID: <1066386735.4777.217.camel@gaston> (raw)
In-Reply-To: <20031017101916.B24238@flint.arm.linux.org.uk>

On Fri, 2003-10-17 at 11:19, Russell King wrote:
> On Thu, Oct 16, 2003 at 03:14:11AM +1000, Anton Blanchard wrote:
> > >From memory at least x86, alpha, ppc32 and ppc64 worked with Andrey's
> > irq consolidation patches. I'll be pushing for it in 2.7 together with
> > some macros to abstract away irq_desc[NR_IRQS] completely. (it will
> > make it easier to support 24 bit irqs on ppc64 and should allow sparc64
> > to use the consolidated irq code).
> 
> (CC list snipped)
> 
> >From what I heard, benh was seriously considering changing ppc64 IRQ
> stuff in 2.7 to use something like the system we have in ARM.

It's on my list of things to investigate once I've reached OzLabs, indeed.

Right now, I have horrible hacks for the "second" OpenPIC in G5s, and
we are indeed reaching the limits of our current irq model. I don't know
yet what direction I will take though. I'm also considering the possibility
of merging ppc32 and ppc64 archs :)

Ben.



  reply	other threads:[~2003-10-17 10:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09  2:00 [RFC] disable_irq()/enable_irq() semantics and ide-probe.c viro
2003-10-09  2:29 ` Linus Torvalds
2003-10-09  2:43   ` viro
2003-10-09  2:53     ` Linus Torvalds
2003-10-09  8:03       ` Russell King
2003-10-09 22:46         ` Zwane Mwaikambo
2003-10-09  8:07       ` Benjamin Herrenschmidt
2003-10-09 15:46       ` viro
2003-10-09 16:01         ` Linus Torvalds
2003-10-09 17:46           ` viro
2003-10-09 18:03             ` Linus Torvalds
2003-10-09 18:27               ` viro
2003-10-09 19:05                 ` Linus Torvalds
2003-10-15 17:14               ` Anton Blanchard
2003-10-17  9:19                 ` Russell King
2003-10-17 10:32                   ` Benjamin Herrenschmidt [this message]
2003-10-09 12:55   ` Roman Zippel
  -- strict thread matches above, loose matches on Subject: below --
2003-10-09 16:10 Manfred Spraul
2003-10-09 16:38 ` Jeff Garzik
2003-10-09 16:57   ` Benjamin Herrenschmidt
2003-10-09 17:03     ` Jeff Garzik
2003-10-09 17:07       ` Benjamin Herrenschmidt
2003-10-09 17:16         ` Jeff Garzik
2003-10-09 17:29   ` Linus Torvalds
2003-10-09 17:52     ` Jeff Garzik

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=1066386735.4777.217.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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