[RFC PATCH 0/8] *** Per context fencing ***
Gurchetan Singh
gurchetansingh at chromium.org
Tue Mar 10 01:08:10 UTC 2020
We don't want fences from different 3D contexts/processes (GL, VK) to
be on the same timeline. Sending this out as a RFC to solicit feedback
on the general approach.
Gurchetan Singh (8):
drm/virtio: use fence_id when processing fences
drm/virtio: allocate a fence context for every 3D context
drm/virtio: plumb virtio_gpu_fpriv to virtio_gpu_fence_alloc
drm/virtio: rename sync_seq and last_seq
drm/virtio: track fence_id in virtio_gpu_fence
virtio/drm: rework virtio_fence_signaled
drm/virtio: check context when signaling
drm/virtio: enable per context fencing
drivers/gpu/drm/virtio/virtgpu_debugfs.c | 4 +-
drivers/gpu/drm/virtio/virtgpu_drv.h | 12 +++--
drivers/gpu/drm/virtio/virtgpu_fence.c | 66 ++++++++++++++++--------
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 9 ++--
drivers/gpu/drm/virtio/virtgpu_kms.c | 1 +
drivers/gpu/drm/virtio/virtgpu_plane.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_vq.c | 4 +-
7 files changed, 62 insertions(+), 36 deletions(-)
--
2.25.1.481.gfbce0eb801-goog
More information about the dri-devel
mailing list