diff options
| author | Marc-André Lureau | 2021-03-11 09:11:37 +0100 |
|---|---|---|
| committer | Marc-André Lureau | 2021-12-21 07:50:21 +0100 |
| commit | f6413cbfd0b3a3f85ebaf9fe13494af1dad916bb (patch) | |
| tree | 89ce165cccf3618b10703f2b01c20047ea63b17f /hw/display/vhost-user-gpu.c | |
| parent | ui: add a gl-unblock warning timer (diff) | |
| download | qemu-f6413cbfd0b3a3f85ebaf9fe13494af1dad916bb.tar.gz qemu-f6413cbfd0b3a3f85ebaf9fe13494af1dad916bb.tar.xz qemu-f6413cbfd0b3a3f85ebaf9fe13494af1dad916bb.zip | |
ui: simplify gl unblock & flush
GraphicHw.gl_flushed was introduced to notify the
device (vhost-user-gpu) that the GL resources (the display scanout) are
no longer needed.
It was decoupled from QEMU own gl-blocking mechanism, but that
difference isn't helping. Instead, we can reuse QEMU gl-blocking and
notify virtio_gpu_gl_flushed() when unblocking (to unlock
vhost-user-gpu).
An extra block/unblock is added arount dpy_gl_update() so existing
backends that don't block will have the flush event handled. It will
also help when there are no backends associated.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'hw/display/vhost-user-gpu.c')
| -rw-r--r-- | hw/display/vhost-user-gpu.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/hw/display/vhost-user-gpu.c b/hw/display/vhost-user-gpu.c index 49df56cd14..09818231bd 100644 --- a/hw/display/vhost-user-gpu.c +++ b/hw/display/vhost-user-gpu.c @@ -254,8 +254,8 @@ vhost_user_gpu_handle_display(VhostUserGPU *g, VhostUserGpuMsg *msg) vhost_user_gpu_unblock(g); break; } - dpy_gl_update(con, m->x, m->y, m->width, m->height); g->backend_blocked = true; + dpy_gl_update(con, m->x, m->y, m->width, m->height); break; } case VHOST_USER_GPU_UPDATE: { |