CHROMIUM: radv: Wait on Android acquire fence on CPU.
This works around stuck fences. Waiting on the CPU here can be a
"Quality of Implementation" issue and might result in lower perf.
However, this is overall very unlikely and this is the same behavior
as the Intel driver does so this is very low risk.
BUG=b:166193448
TEST=cts-tradefed run commandAndExit cts -m CtsDeqpTestCases -t dEQP-VK.wsi.*
multiple times (with & without reboots)
Change-Id: I58fa67788f314b2a91ffcca83fdb47ee81c44fb3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/mesa/+/2426495
Tested-by: Bas Nieuwenhuizen <basni@chromium.org>
Reviewed-by: Drew Davenport <ddavenport@chromium.org>
Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org>
Commit-Queue: Drew Davenport <ddavenport@chromium.org>
(cherry picked from commit dd34c79c20c1baf5c584edada8b2f0fa08868145)
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/mesa/+/2436460
Commit-Queue: Bas Nieuwenhuizen <basni@chromium.org>
1 file changed