loader/dri3: Don't wait for fence of old buffer when re-allocating it
authorMichel Dänzer <michel.daenzer@amd.com>
Tue, 4 Sep 2018 16:18:57 +0000 (18:18 +0200)
committerMichel Dänzer <michel@daenzer.net>
Wed, 12 Sep 2018 14:55:09 +0000 (16:55 +0200)
We only need to wait for the fence before drawing to a buffer, not
before reading from it.

This might avoid hangs when re-allocating the fake front buffer, similar
to the previous change. But I haven't seen any evidence that this was
actually happening in practice.

Tested-by: Olivier Fourdan <ofourdan@redhat.com>
src/loader/loader_dri3_helper.c

index 258678a6662f0bf0dde60e6372ac09364c857bb9..f641a34e6d1e036de73dbaaa2c3aeec49a742851 100644 (file)
@@ -1777,7 +1777,6 @@ dri3_get_buffer(__DRIdrawable *driDrawable,
           && buffer) {
 
          /* Fill the new buffer with data from an old buffer */
-         dri3_fence_await(draw->conn, draw, buffer);
          if (!loader_dri3_blit_image(draw,
                                      new_buffer->image,
                                      buffer->image,