linux-kernel - Re: [patch 23/26] x64, x2apic/intr-remap: MSI and MSI-X support for interrupt remapping infrastructure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 11 Jul 2008 16:07:12 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	"mingo@...e.hu" <mingo@...e.hu>, "hpa@...or.com" <hpa@...or.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
	"steiner@....com" <steiner@....com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [patch 23/26] x64, x2apic/intr-remap: MSI and MSI-X support for interrupt remapping infrastructure

On Fri, Jul 11, 2008 at 01:59:24AM -0700, Eric W. Biederman wrote:
> What I am ultimately looking for is the x86 iommu irq mapping api.
> And how we handle irqs in the context of it.
> 
> So as a start I think we can create x86_map_irq, as I suggested.

Sure. Will probably introduce irq_mapping_ops (which may be as simple as
ops containing specific msi_compose_msg, ioapic_compose_rte, etc). This
should simiplify the setup code. I will look into this and post these patches
next week.

> Since we have the pci dev to lookup the iommu then we really shouldn't

Not all irq's in the platform will be remapped, for example, interrupts
generated by IOMMU itself are not remapped. And all irq's don't have
corresponding pci dev, like IO-APIC, MSI etc.

> need multiple irq_chip structures (although it may be worth it if we
> can detect we can optimize irq migration).

Depending on the IOMMU/hardware, they may define different irq_chip's
if they add/simplify functionality, or may  use existing irq_chip's.

thanks,
suresh
--
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/