drm/virtio: implement blob resources: fix stride discrepancy

Browse source

The old transfer ioctls may work on blob resources, and there is no
TRANSFER_BLOB hypercall now for simplicity.

The guest may have a image view on the blob resources such that the
stride is not equal to width * bytes_per_pixel.

For host-only blobs, we can repurpose the transfer ioctls to synchronize
caches as well.  For guest-only blobs, these operations are undefined
for now so leave them out.

Also, with seamless Wayland integration between guest/host looking
increasingly attractive, it also makes sense to keep track of
one value for stride.

Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
Acked-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20200924003214.662-16-gurchetansingh@chromium.org
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>

...

This commit is contained in:

Gurchetan Singh 2020-09-23 17:32:11 -07:00 • committed by Gerd Hoffmann

parent 1e2554f49e

commit 50c3d1938e

3 changed files with 47 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4

drivers/gpu/drm/virtio/virtgpu_drv.h

View file

35

drivers/gpu/drm/virtio/virtgpu_ioctl.c

View file

14

drivers/gpu/drm/virtio/virtgpu_vq.c

View file