diff options
| author | Michel Dänzer <[email protected]> | 2018-09-04 18:18:57 +0200 |
|---|---|---|
| committer | Michel Dänzer <[email protected]> | 2018-09-12 16:55:09 +0200 |
| commit | e34dd4f5084c73c0a2fcadf783e8f7d8199bb5ca (patch) | |
| tree | ddfd810f32e0fc8fee2959c8917ea7b610c7480c | |
| parent | aefac10fecc9ec70feb5923ce3200902f67182ba (diff) | |
loader/dri3: Don't wait for fence of old buffer when re-allocating it
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 <[email protected]>
| -rw-r--r-- | src/loader/loader_dri3_helper.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/loader/loader_dri3_helper.c b/src/loader/loader_dri3_helper.c index 258678a6662..f641a34e6d1 100644 --- a/src/loader/loader_dri3_helper.c +++ b/src/loader/loader_dri3_helper.c @@ -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, |