summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/virtio/virtgpu_drv.c
diff options
context:
space:
mode:
authorGurchetan Singh <gurchetansingh@chromium.org>2021-09-21 16:20:20 -0700
committerGerd Hoffmann <kraxel@redhat.com>2021-09-29 09:22:31 +0200
commitbbf588d7d4ed5912481b12a31ffadec359fb8cae (patch)
tree4c5c88a4d54a8ca8d0af9abb2ad3086649a5bd16 /drivers/gpu/drm/virtio/virtgpu_drv.c
parente8b6e76f69a4336076a2e639d211c4cf3447ce87 (diff)
downloadlinux-bbf588d7d4ed5912481b12a31ffadec359fb8cae.tar.gz
linux-bbf588d7d4ed5912481b12a31ffadec359fb8cae.tar.bz2
linux-bbf588d7d4ed5912481b12a31ffadec359fb8cae.zip
drm/virtio: implement context init: stop using drv->context when creating fence
The plumbing is all here to do this. Since we always use the default fence context when allocating a fence, this makes no functional difference. We can't process just the largest fence id anymore, since it's it's associated with different timelines. It's fine for fence_id 260 to signal before 259. As such, process each fence_id individually. Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org> Acked-by: Lingfeng Yang <lfy@google.com> Link: http://patchwork.freedesktop.org/patch/msgid/20210921232024.817-9-gurchetansingh@chromium.org Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/virtio/virtgpu_drv.c')
0 files changed, 0 insertions, 0 deletions