| 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: <20080609184052Z.fujita.tomonori@lab.ntt.co.jp> Date: Mon, 9 Jun 2008 18:36:29 +0900 From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> To: andi@...stfloor.org Cc: grundler@...gle.com, muli@...ibm.com, fujita.tomonori@....ntt.co.jp, linux-kernel@...r.kernel.org, mgross@...ux.intel.com, linux-scsi@...r.kernel.org Subject: Re: Intel IOMMU (and IOMMU for Virtualization) performances On Mon, 09 Jun 2008 10:17:11 +0200 Andi Kleen <andi@...stfloor.org> wrote: > "Grant Grundler" <grundler@...gle.com> writes: > > > > The historical DMA mapping "failure mode" is a kernel panic. Resizing or > > Hasn't been for a long time, except in some extreme cases. All drivers > are expected to check return values for a long time now. Agreed, but I think that lots of network drivers still assume that DMA mapping always succeeds (they don't check return values). Most of the SCSI drivers were fixed in this regard. Very old HBA drivers (that are unlikely to be used with an IOMMU) just crashes. Recent HBA drivers can handle the dma mapping failure (as far as I know, the only exception is cciss. Old IOMMU code has "failure mode" but new IOMMU code like VT-d doesn't crash on the failure. Now drivers need to handle the dma mapping failure properly. -- 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