summaryrefslogtreecommitdiff
path: root/drivers/s390
diff options
context:
space:
mode:
authorYi Liu <yi.l.liu@intel.com>2022-12-02 05:54:01 -0800
committerJason Gunthorpe <jgg@nvidia.com>2022-12-02 11:49:26 -0400
commit4dc334cab1c34efb17fa6cd10b12fbc9458e5760 (patch)
treeff48fe6a1a7b14a8ac38c033862d8e22b68e6963 /drivers/s390
parent1a65c39e2a521d2fb97d7ba5b16321dde057eb06 (diff)
downloadlwn-4dc334cab1c34efb17fa6cd10b12fbc9458e5760.tar.gz
lwn-4dc334cab1c34efb17fa6cd10b12fbc9458e5760.zip
i915/gvt: Move gvt mapping cache initialization to intel_vgpu_init_dev()
vfio container registers .dma_unmap() callback after the device is opened. So it's fine for mdev drivers to initialize internal mapping cache in .open_device(). See vfio_device_container_register(). Now with iommufd an access ops with an unmap callback is registered when the device is bound to iommufd which is before .open_device() is called. This implies gvt's .dma_unmap() could be called before its internal mapping cache is initialized. The fix is moving gvt mapping cache initialization to vGPU init. While at it also move ptable initialization together. Link: https://lore.kernel.org/r/20221202135402.756470-2-yi.l.liu@intel.com Reviewed-by: Zhi Wang <zhi.a.wang@intel.com> Reviewed-by: Zhenyu Wang <zhenyuw@linux.intel.com> Signed-off-by: Yi Liu <yi.l.liu@intel.com> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'drivers/s390')
0 files changed, 0 insertions, 0 deletions