Bug 97461:
FS-UAE waits forever with glClientWaitSync() when using glFenceSync() on amdgpu/radeonsi -
Lem <lem.jjr@gmail.com> -
8/24/2016
Back to Bug |
Your Reviews |
Help
Attachment 126023:
possible fix -
Marek Olšák <maraeo@gmail.com> -
8/25/2016
(
View
)
Close Quick Help
- From the Overview page, you can add a more generic overview comment that will appear at the beginning of your review.
- To comment on a specific lines in the patch, first select the filename from the file navigation links.
- Then double click the line you want to review and a comment box will appear below the line.
- When the review is complete and you publish it, the overview comment and all line specific comments with their context,
will be combined together into a single review comment on the bug report.
- For more detailed instructions, read the Splinter
help page.
From: =?UTF-8?q?Marek=20Ol=C5=A1=C3=A1k?= <marek.olsak@amd.com>
Date: Thu, 25 Aug 2016 01:26:54 +0200
Subject: [PATCH] gallium/radeon: unify and simplify checking for an empty gfx
IB
We can take advantage of the fact that multi_fence does the obvious thing
with NULL fences.
This fixes unflushed fences that can get stuck due to empty IBs.
(Restored from draft; last edited )