Fix back-to-back transfer command synchronization hazards
authorJeremy Gebben <jeremyg@lunarg.com>
Wed, 9 Dec 2020 15:12:25 +0000 (08:12 -0700)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Fri, 18 Dec 2020 08:11:17 +0000 (08:11 +0000)
commitc7b56bbeed1219b409b64ad7b968dce6851b6b23
tree134e97dbfae4cdff110b0e0c9e63bc198754e4fa
parent7408d79306a010870cadc8d49e54daaf107b72bd
Fix back-to-back transfer command synchronization hazards

If 2 transfer commands use the same memory, they need a pipeline barrier
between them.

VK-GL-CTS Issue: 2693

Affects Tests:
dEQP-VK.api.image_clearing.core.clear_depth_stencil_image.remaining_array_layers_twostep.*
dEQP-VK.pipeline.timestamp.transfer_tests.*
dEQP-VK.ycbcr.copy_dimensions.*

Components: Vulkan

Change-Id: I91bf74c63275f6e3dd6c383f59d1f4e9c1aa0982
external/vulkancts/modules/vulkan/api/vktApiImageClearingTests.cpp
external/vulkancts/modules/vulkan/pipeline/vktPipelineTimestampTests.cpp
external/vulkancts/modules/vulkan/ycbcr/vktYCbCrCopyTests.cpp