On Wed, Oct 28, 2015 at 03:30:01PM +0900, David Woodhouse wrote: > > > +For systems with IOMMU it is assumed all DMA translations use the IOMMU. > > Not entirely true. We have per-device dma_ops on a most architectures > already, and we were just talking about the need to add them to > POWER/SPARC too, because we need to avoid trying to use the IOMMU to > map virtio devices too. SPARC has it's implementation under arch/sparc for dma_ops (sun4v_dma_ops). Some drivers use IOMMU under SPARC for example ixgbe (Intel 10G ETH). Some, like IB, suffer from IOMMU MAP setup/tear-down & limited address range. On SPARC IOMMU bypass is not total bypass of the IOMMU but rather much simple translation that does not require any complex translations tables. > > As we look at that (and make the per-device dma_ops a generic thing > rather than per-arch), we should probably look at folding your case in > too. Whether to use IOMMU or not for DMA is up to the driver. The above example show real situation where one driver can use IOMMU and the other can't. It seems that the device cannot know when to use IOMMU bypass and when not. Even in the driver we can decide to DMA map some buffers using IOMMU translation and some as IOMMU bypass. Do you agree that we need this attribute in the generic DMA API? > > -- > dwmw2 > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
