linux-kernel - Re: PCIE

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]

Message-ID: <aday7j921w8.fsf@cisco.com>
Date:	Sun, 27 May 2007 18:05:43 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	David Miller <davem@...emloft.net>, abraham.manu@...il.com,
	greg@...ah.com, linux-pci@...ey.karlin.mff.cuni.cz,
	linux-kernel@...r.kernel.org
Subject: Re: PCIE

 > Presumably we need something like IRQF_MSI which can be set as
 > appropriate depending on the architecture?

Unfortunately I don't think it's that simple -- drivers would have to
do something like

	if (IRQF_MSI == IRQF_SHARED) {
		// lose MSI optimizations, do an MMIO read, etc.
	} else...

As I said I think that if we're running on a system where MSI
interrupts might be shared, we should just have pci_enable_msi() fail
so drivers fall back to their usual interrupt handler.
-
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/