Hi Lyude, and thanks for taking a look.
> -#if IS_ENABLED(CONFIG_SWIOTLB) && IS_ENABLED(CONFIG_X86)
> - need_swiotlb = is_swiotlb_active(dev->dev);
> -#endif
> -
> ret = ttm_device_init(&drm->ttm.bdev, &nouveau_bo_driver, drm->dev->dev,
> - dev->anon_inode->i_mapping,
> - dev->vma_offset_manager, need_swiotlb,
> - drm->client.mmu.dmabits <= 32);
> + dev->anon_inode->i_mapping,
> + dev->vma_offset_manager,
> + nouveau_drm_use_coherent_gpu_mapping(drm),
> + drm->client.mmu.dmabits <= 32);
This will break setups for two reasons:
- swiotlb is not only used to do device addressing limitations, so
this will not catch the case of interconnect addressing limitations
or forced bounce buffering which used used e.g. in secure VMs.
- we might need bouncing for any DMA address below the physical
address limit of the CPU
But more fundamentally the use_dma32 argument to ttm_device_init
is rather broken, as the onlyway to get a memory allocation that
fits the DMA addressing needs of a device is to use the proper
DMA mapping helpers. i.e. ttm_pool_alloc_page really needs to use
dma_alloc_pages instead of alloc_pages as a first step. That way
all users of the TTM pool will always get dma addressable pages
and there is no need to guess the addressing limitations.
The use_dma_alloc is then only needed for users that require coherent
memory and are willing to deal with the limitations that this entails
(e.g. no way to get at the page struct).
> if (ret) {
> NV_ERROR(drm, "error initialising bo driver, %d\n", ret);
> return ret;
> --
> 2.35.3
---end quoted text---
