On Thu, Mar 04, 2021 at 03:25:27PM +0000, Robin Murphy wrote:

On 2021-03-01 08:42, Christoph Hellwig wrote:

quoted

Use explicit methods for setting and querying the information instead.

Now that everyone's using iommu-dma, is there any point in bouncing this 
through the drivers at all? Seems like it would make more sense for the x86 
drivers to reflect their private options back to iommu_dma_strict (and 
allow Intel's caching mode to override it as well), then have 
iommu_dma_init_domain just test !iommu_dma_strict && 
domain->ops->flush_iotlb_all.

Indeed.  I switch to that.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization