[PATCH v3 2/2] drm/virtio: set max_segment
Gerd Hoffmann
kraxel at redhat.com
Mon Sep 7 06:33:43 UTC 2020
When initializing call virtio_max_dma_size() to figure the scatter list
limit. Needed to make virtio-gpu work properly with SEV.
v2: place max_segment in drm driver not gem object.
Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>
---
drivers/gpu/drm/virtio/virtgpu_kms.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/virtio/virtgpu_kms.c b/drivers/gpu/drm/virtio/virtgpu_kms.c
index 75d0dc2f6d28..151471acdfcf 100644
--- a/drivers/gpu/drm/virtio/virtgpu_kms.c
+++ b/drivers/gpu/drm/virtio/virtgpu_kms.c
@@ -167,6 +167,7 @@ int virtio_gpu_init(struct drm_device *dev)
DRM_ERROR("failed to alloc vbufs\n");
goto err_vbufs;
}
+ dev->max_segment = virtio_max_dma_size(vgdev->vdev);
/* get display info */
virtio_cread_le(vgdev->vdev, struct virtio_gpu_config,
--
2.27.0
More information about the dri-devel
mailing list