aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/virtio/virtgpu_kms.c
diff options
context:
space:
mode:
authorGerd Hoffmann <kraxel@redhat.com>2020-09-07 13:24:25 +0200
committerGerd Hoffmann <kraxel@redhat.com>2020-09-09 07:58:56 +0200
commit707d561f77b5e2a6f90c9786bee44ee7a8dedc7e (patch)
tree0d61c5038b1f4e8d9f5c0640b7349058600cb9d7 /drivers/gpu/drm/virtio/virtgpu_kms.c
parentdrm/ttm: drop the tt backend function paths. (diff)
downloadlinux-dev-707d561f77b5e2a6f90c9786bee44ee7a8dedc7e.tar.xz
linux-dev-707d561f77b5e2a6f90c9786bee44ee7a8dedc7e.zip
drm: allow limiting the scatter list size.
Add drm_device argument to drm_prime_pages_to_sg(), so we can call dma_max_mapping_size() to figure the segment size limit and call into __sg_alloc_table_from_pages() with the correct limit. This fixes virtio-gpu with sev. Possibly it'll fix other bugs too given that drm seems to totaly ignore segment size limits so far ... v2: place max_segment in drm driver not gem object. v3: move max_segment next to the other gem fields. v4: just use dma_max_mapping_size(). Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: http://patchwork.freedesktop.org/patch/msgid/20200907112425.15610-2-kraxel@redhat.com
Diffstat (limited to 'drivers/gpu/drm/virtio/virtgpu_kms.c')
0 files changed, 0 insertions, 0 deletions