diff options
| author |   Gurchetan Singh <gurchetansingh@chromium.org> | 2021-09-21 16:20:23 -0700 |
|---|---|---|
| committer |   Gerd Hoffmann <kraxel@redhat.com> | 2021-09-29 09:22:31 +0200 |
| commit | cd7f5ca33585918febe5e2f6dc090a21cfa775b0 (patch) | |
| tree | 6bbee480a5b3c6073de5ffcdea6c9be2bd3f6771 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | drm/virtio: implement context init: handle VIRTGPU_CONTEXT_PARAM_POLL_RINGS_MASK (diff) | |
| download | wireguard-linux-cd7f5ca33585918febe5e2f6dc090a21cfa775b0.tar.xz wireguard-linux-cd7f5ca33585918febe5e2f6dc090a21cfa775b0.zip | |
drm/virtio: implement context init: add virtio_gpu_fence_event
Similar to DRM_VMW_EVENT_FENCE_SIGNALED. Sends a pollable event
to the DRM file descriptor when a fence on a specific ring is
signaled.
One difference is the event is not exposed via the UAPI -- this is
because host responses are on a shared memory buffer of type
BLOB_MEM_GUEST [this is the common way to receive responses with
virtgpu]. As such, there is no context specific read(..)
implementation either -- just a poll(..) implementation.
Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
Acked-by: Nicholas Verne <nverne@chromium.org>
Link: http://patchwork.freedesktop.org/patch/msgid/20210921232024.817-12-gurchetansingh@chromium.org
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions