| 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
| ||
|
Message-ID: <20070528041802.GB711@colo.lackof.org> Date: Sun, 27 May 2007 22:18:02 -0600 From: Grant Grundler <grundler@...isc-linux.org> To: Roland Dreier <rdreier@...co.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 On Sun, May 27, 2007 at 06:03:29PM -0700, Roland Dreier wrote: ... > > I can imagine many systems where the cpu simply doesn't have enough > > interrupt pins to uniquely identify every possible MSI interrupt > > source. > > I have a hard time imagining a PCI host bus controller that converts > MSI interrupts back to wire interrupts that go to pins on the CPU. > For one thing it would be hard to maintain the guarantee that > MSI interrupts can't pass DMAs. Whatever converts the MSI back to CPU IRQ pins would have to participate in the "cache coherency domain". This would avoid issues around DMA ordering. It _could_ be on the same silicon as the PCI Host bus controller as long as the above is true. > And it would be an absolutely silly architecture too. While I agree it's silly, it might be cheaper if any patents are involved, it reduces complexity, power consumption or anything else that costs time/money. thanks, grant - 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