radv: force cs/ps/l2 flush at end of command stream. (v2)
authorDave Airlie <airlied@redhat.com>
Wed, 26 Jul 2017 03:37:53 +0000 (04:37 +0100)
committerDave Airlie <airlied@redhat.com>
Wed, 9 Aug 2017 22:19:15 +0000 (23:19 +0100)
commit82ba384c10d598bee4786ef5f79e92a0e7b53892
treee6541bee100d67400afc3c9e03a1612db345f270
parent24a799ad35a824fba94062f9b018f603717ed145
radv: force cs/ps/l2 flush at end of command stream. (v2)

This seems like a workaround, but we don't see the bug on CIK/VI.

On SI with the dEQP-VK.memory.pipeline_barrier.host_read_transfer_dst.*
tests, when one tests complete, the first flush at the start of the next
test causes a VM fault as we've destroyed the VM, but we end up flushing
the compute shader then, and it must still be in the process of doing
something.

Could also be a kernel difference between SI and CIK.

v2: hit this with a bigger hammer. This fixes a bunch of hangs
in the vk cts with the robustness tests.

Fixes: f4e499ec791 ("radv: add initial non-conformant radv vulkan driver")
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101334
Acked-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Signed-off-by: Dave Airlie <airlied@redhat.com>
src/amd/vulkan/radv_cmd_buffer.c