[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m163rc6kgh.fsf@frodo.ebiederm.org>
Date: Fri, 11 Jul 2008 16:59:42 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: Matthew Wilcox <matthew@....cx>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"grundler@...isc-linux.org" <grundler@...isc-linux.org>,
"mingo@...e.hu" <mingo@...e.hu>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"jgarzik@...ox.com" <jgarzik@...ox.com>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
"benh@...nel.crashing.org" <benh@...nel.crashing.org>,
"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
"rdunlap@...otime.net" <rdunlap@...otime.net>,
"mtk.manpages@...il.com" <mtk.manpages@...il.com>
Subject: Re: Multiple MSI, take 3
Suresh Siddha <suresh.b.siddha@...el.com> writes:
> And why do we need to mask/unmask the device in the interrupt-remapping case?
Why do we ever? It is part of the linux irq API and people wind up using
it in all kinds of strange ways.
One of the more surprising uses I have see is for the real time kernel
people mask the irq, wake up a kernel thread (to handle the irq), then
ack the irq and get out of the interrupt handler. It looked like
people working on UIO were starting to implement something similar.
>> Speaking of. How many interrupt targets does the dmar iommu have
>> for interrupts? 16K?
>
> There can be multiple interrupt-remapping units in the platform and
> each of table in the remapping unit has max 64K entries.
Thanks. That should last us for a little while. :)
Eric
--
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