VK_KHR_incremental_present: Trigger the fence off vkQueueSubmit
authorJason Ekstrand <jason.ekstrand@intel.com>
Fri, 6 Oct 2017 23:10:26 +0000 (16:10 -0700)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Sat, 7 Oct 2017 15:50:07 +0000 (11:50 -0400)
commitdb916576a76a17c02c14390fc5d5b3db1488d1d2
treec3aea582a1af907b3750a375d4679e909fc7b0b9
parent66b4bb72aadcdacbd7cfc8d8ee5573ffc181b3d0
VK_KHR_incremental_present: Trigger the fence off vkQueueSubmit

Previously, the tests were using AcquireNextImage to trigger the fence
and using it to guard the vkFreeCommandBuffers call.  However, the
acquire fence tells you when the PE is done with an image and when you
can start rendering to it.  This meant that the test was waiting for the
start of the previous frame's rendering not the end before deleting the
previous frame's command buffer.  This meant that the previous frame's
rendering could still be active on the GPU when the command buffer was
freed.  By triggering the fence off of the vkQueueSubmit, we wait for
the end of the previous frame's rendering before freeing its command
buffer.

VK-GL-CTS issue: 756

Component: Vulkan

Affects:
dEQP-VK.wsi.*.incremental_present.*

Change-Id: I87b25eb2a25e4ae48c8c527d5d63c45d89a31a30
external/vulkancts/modules/vulkan/wsi/vktWsiIncrementalPresentTests.cpp