Hi,
On 11/28/20 6:15 PM, Christoph Hellwig wrote:
> Can you give this one-liner a spin?
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index c6622011d4938c..e889111b55c71d 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -4007,6 +4007,7 @@ static const struct dma_map_ops bounce_dma_ops = {
> .alloc_pages = dma_common_alloc_pages,
> .free_pages = dma_common_free_pages,
> .dma_supported = dma_direct_supported,
> + .max_mapping_size = swiotlb_max_mapping_size,
> };
>
> static inline int iommu_domain_cache_init(void)
>
I'm afraid that this does not help.
Also I still find it somewhat wrong that the use of scsi_add_host_with_dma()
in uas.c, which then passed the XHCI controller as dma-dev is causing changes
to the DMA settings of the XHCI controller, impacting *other* USB devices
and these changes also are permanent, they stay around even after unbinding
the uas driver.
This just feels wrong on many levels. If some changes to the XHCI controllers
DMA settings are necessary for better uas performance then these changes
really should be made inside the XHCI driver, so that they always apply and
not have this weirdness going on where binding one USB driver permanently
changes the behavior of the entire USB bus (until rebooted).
Querying the DMA settings of the XHCI controller in the uas driver is fine,
but changing them seems like a big nono to me.
Regards,
Hans
