BACKPORT: FROMGIT: drm/virtio: implement blob resources: fix stride discrepancy

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>
(cherry picked from commit 50c3d1938ee380e2d24714ea7058d2d3fc2662de
 git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

 master)

Conflicts:
   drivers/gpu/drm/virtio/virtgpu_vq.c

BUG=b:171715474
TEST=compile

Change-Id: I754bc83ccfe119f2dca962f51e9716c42738ce7b
Signed-off-by: Guenter Roeck <groeck@chromium.org>
(cherry picked from commit b37977bde3c51ced1566806e05528ffb207992fe)