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>
Tue, 10 Oct 2017 07:11:07 +0000 (03:11 -0400)
commit438ea0888e8ccae0249f8520b5c40e06ccbfc16c
treee35d946270d25100bce7958d97effeec5ae70e0a
parentc0b59025694fd9cecfa19037689b5ad5500e08e4
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
(cherry picked from commit db916576a76a17c02c14390fc5d5b3db1488d1d2)
external/vulkancts/modules/vulkan/wsi/vktWsiIncrementalPresentTests.cpp