linux.git/drivers/gpu/drm/virtio/virtgpu_vq.c, branch v5.5

drm/virtio: move byteorder handling into virtio_gpu_cmd_transfer_to_host_2d function

2019-10-22T09:34:03+00:00

Be consistent with the rest of the code base.

Signed-off-by: Gerd Hoffmann 
Reviewed-by: Daniel Vetter 
Link: http://patchwork.freedesktop.org/patch/msgid/20191018122352.17019-1-kraxel@redhat.com

drm/virtio: Fix warning in virtio_gpu_queue_fenced_ctrl_buffer.

2019-09-13T07:11:56+00:00

Fix warning introduced with commit e1218b8c0cc1
("drm/virtio: Use vmalloc for command buffer allocations.")
from drm-misc-next.

Signed-off-by: David Riley 
Reviewed-by: Chia-I Wu 
Link: http://patchwork.freedesktop.org/patch/msgid/20190912160048.212495-1-davidriley@chromium.org
Signed-off-by: Gerd Hoffmann

drm/virtio: Use vmalloc for command buffer allocations.

2019-09-12T07:49:24+00:00

Userspace requested command buffer allocations could be too large
to make as a contiguous allocation.  Use vmalloc if necessary to
satisfy those allocations.

Signed-off-by: David Riley 
Link: http://patchwork.freedesktop.org/patch/msgid/20190911181403.40909-3-davidriley@chromium.org
Signed-off-by: Gerd Hoffmann

drm/virtio: Rewrite virtio_gpu_queue_ctrl_buffer using fenced version.

2019-09-12T07:49:24+00:00

Factor function in preparation to generating scatterlist prior to locking.

Signed-off-by: David Riley 
Link: http://patchwork.freedesktop.org/patch/msgid/20190911181403.40909-2-davidriley@chromium.org
Signed-off-by: Gerd Hoffmann

drm/virtio: fix command submission with objects but without fence.

2019-09-06T05:23:37+00:00

Only call virtio_gpu_array_add_fence if we actually have a fence.

Fixes: da758d51968a ("drm/virtio: rework virtio_gpu_execbuffer_ioctl fencing")
Signed-off-by: Gerd Hoffmann 
Reviewed-by: Chia-I Wu 
Link: http://patchwork.freedesktop.org/patch/msgid/20190904074828.32502-1-kraxel@redhat.com

drm/virtio: add worker for object release

2019-09-04T04:54:12+00:00

Move object release into a separate worker.  Releasing objects requires
sending commands to the host.  Doing that in the dequeue worker will
cause deadlocks in case the command queue gets filled up, because the
dequeue worker is also the one which will free up slots in the command
queue.

Reported-by: Chia-I Wu 
Signed-off-by: Gerd Hoffmann 
Reviewed-by: Chia-I Wu 
Tested-by: Chia-I Wu 
Link: http://patchwork.freedesktop.org/patch/msgid/20190830060116.10476-1-kraxel@redhat.com

drm/virtio: switch from ttm to gem shmem helpers

2019-09-04T04:54:11+00:00

virtio-gpu basically needs a sg_table for the bo, to tell the host where
the backing pages for the object are.  So the gem shmem helpers are a
perfect fit.  Some drm_gem_object_funcs need thin wrappers to update the
host state, but otherwise the helpers handle everything just fine.

Once the fencing was sorted the switch was surprisingly easy and for the
most part just removing the ttm code.

v4: fix drm_gem_object_funcs name.

Signed-off-by: Gerd Hoffmann 
Acked-by: Daniel Vetter 
Reviewed-by: Chia-I Wu 
Link: http://patchwork.freedesktop.org/patch/msgid/20190829103301.3539-15-kraxel@redhat.com

drm/virtio: rework virtio_gpu_cmd_context_{attach, detach}_resource

2019-09-04T04:54:10+00:00

Switch to the virtio_gpu_array_* helper workflow.

Signed-off-by: Gerd Hoffmann 
Reviewed-by: Chia-I Wu 
Link: http://patchwork.freedesktop.org/patch/msgid/20190829103301.3539-13-kraxel@redhat.com

drm/virtio: rework virtio_gpu_transfer_to_host_ioctl fencing

2019-09-04T04:54:10+00:00

Switch to the virtio_gpu_array_* helper workflow.

Signed-off-by: Gerd Hoffmann 
Reviewed-by: Chia-I Wu 
Link: http://patchwork.freedesktop.org/patch/msgid/20190829103301.3539-12-kraxel@redhat.com

drm/virtio: rework virtio_gpu_transfer_from_host_ioctl fencing

2019-09-04T04:54:10+00:00

Switch to the virtio_gpu_array_* helper workflow.

Signed-off-by: Gerd Hoffmann 
Reviewed-by: Chia-I Wu 
Link: http://patchwork.freedesktop.org/patch/msgid/20190829103301.3539-11-kraxel@redhat.com