diff options
| author | Gurchetan Singh <gurchetansingh@chromium.org> | 2021-11-22 15:22:09 -0800 |
|---|---|---|
| committer | Gerd Hoffmann <kraxel@redhat.com> | 2021-11-29 11:46:32 +0100 |
| commit | 7e78781df491e4beb475bac22e6c44236a5002d7 (patch) | |
| tree | 2c1717c4b609d95cfa652348c467de517e2ddee8 /lib/test_ida.c | |
| parent | e048834c209a02e3776bcc47d43c6d863e3a67ca (diff) | |
| download | linux-stable-7e78781df491e4beb475bac22e6c44236a5002d7.tar.gz linux-stable-7e78781df491e4beb475bac22e6c44236a5002d7.tar.bz2 linux-stable-7e78781df491e4beb475bac22e6c44236a5002d7.zip | |
drm/virtgpu api: define a dummy fence signaled event
The current virtgpu implementation of poll(..) drops events
when VIRTGPU_CONTEXT_PARAM_POLL_RINGS_MASK is enabled (otherwise
it's like a normal DRM driver).
This is because paravirtualized userspaces receives responses in a
buffer of type BLOB_MEM_GUEST, not by read(..).
To be in line with other DRM drivers and avoid specialized behavior,
it is possible to define a dummy event for virtgpu. Paravirtualized
userspace will now have to call read(..) on the DRM fd to receive the
dummy event.
Fixes: b10790434cf2 ("drm/virtgpu api: create context init feature")
Reported-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/20211122232210.602-2-gurchetansingh@google.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'lib/test_ida.c')
0 files changed, 0 insertions, 0 deletions