| 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: <1252328070.4483.569.camel@macbook.infradead.org> Date: Mon, 07 Sep 2009 13:54:30 +0100 From: David Woodhouse <dwmw2@...radead.org> To: Joerg Roedel <joerg.roedel@....com> Cc: iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/8] Passthrough support for AMD-IOMMU (AMD-Vi) On Fri, 2009-09-04 at 11:36 +0200, Joerg Roedel wrote: > > this series of patches implement iommu=pt support for AMD IOMMU (AMD-Vi). If > this option is passed on the kernel command line, the AMD-Vi driver will not > register itself as the dma_ops backend and allows all devices unlimited access > to main memory as long as no other kernel part (currently only KVM will do so) > assigns the device to another domain using the IOMMU-API. The Intel IOMMU used to behave like that in passthrough mode, but I've now changed it. Now, it will still register itself as the dma_ops backend, and it won't actually bypass the IOMMU for devices with a limited dma_mask. So you don't end up having to use swiotlb for those (which wasn't working anyway, iirc). The devices for which you actually care about performance are still going to end up with the passthrough mapping as you desire, anyway. -- David Woodhouse Open Source Technology Centre David.Woodhouse@...el.com Intel Corporation -- 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