[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1215085266.19689.19.camel@pasglop>
Date: Thu, 03 Jul 2008 21:41:06 +1000
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Matthew Wilcox <matthew@....cx>
Cc: Arnd Bergmann <arnd@...db.de>, michaele@....ibm.com,
linux-pci@...r.kernel.org,
Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
David Miller <davem@...emloft.net>,
Dan Williams <dan.j.williams@...el.com>,
Martine.Silbermann@...com, linux-kernel@...r.kernel.org
Subject: Re: Multiple MSI
On Thu, 2008-07-03 at 05:31 -0600, Matthew Wilcox wrote:
> On Thu, Jul 03, 2008 at 07:17:00PM +1000, Benjamin Herrenschmidt wrote:
> > > Some years ago, we had discussions about getting rid of IRQ numbers
> > > altogether, or at least the requirement to have device drivers know
> > > about them. Does anyone remember what happened to that idea?
> >
> > I think it's not totally dead. Last I heard, someone (jgarzik ?) was
> > slowly, bit by bit, removing the dependencies on the irq argument on irq
> > handlers which is one step in the direction.
>
> I think that project's dead, Jim. http://lkml.org/lkml/2008/4/22/578
Ouch, missed that one... sad, would have been a good idea in the long
run. irq_desc array is a big PITA.
> You can't do that. /proc/interrupts is so terribly useful for a
> sysadmin that you can't remove information from it.
You can create a new one with informations about the new stuff..
Anyway, looks like it's not happening and we'll be stuck with the bloody
array for the time being. Crap.
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists