diff options
author | Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> | 2023-02-24 18:34:50 +0300 |
---|---|---|
committer | Dmitry Osipenko <dmitry.osipenko@collabora.com> | 2023-02-27 02:39:24 +0300 |
commit | a54bace095d00e9222161495649688bc43de4dde (patch) | |
tree | 2e648258b35e3d46cd7127a3280804c6ffd0175c /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | 1b9b4f922f96108da3bb5d87b2d603f5dfbc5650 (diff) | |
download | linux-a54bace095d00e9222161495649688bc43de4dde.tar.xz |
drm/virtio: Pass correct device to dma_sync_sgtable_for_device()
The "vdev->dev.parent" should be used instead of "vdev->dev" as a device
for which to perform the DMA operation in both
virtio_gpu_cmd_transfer_to_host_2d(3d).
Because the virtio-gpu device "vdev->dev" doesn't really have DMA OPS
assigned to it, but parent (virtio-pci or virtio-mmio) device
"vdev->dev.parent" has. The more, the sgtable in question the code is
trying to sync here was mapped for the parent device (by using its DMA OPS)
previously at:
virtio_gpu_object_shmem_init()->drm_gem_shmem_get_pages_sgt()->
dma_map_sgtable(), so should be synced here for the same parent device.
Fixes: b5c9ed70d1a9 ("drm/virtio: Improve DMA API usage for shmem BOs")
Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230224153450.526222-1-olekstysh@gmail.com
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions