From: Samuel Pitoiset Date: Tue, 17 Apr 2018 13:08:11 +0000 (+0200) Subject: radv: make sure to sync after resolving using the compute path X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=796b6f4aab46924f9954c9b2a9821b4706618cab;p=mesa.git radv: make sure to sync after resolving using the compute path This fixes some random CTS failures: dEQP-VK.renderpass.multisample.*. Performing a fast-clear eliminate is still useless, but it seems that we need to sync. Found while running CTS with RADV_DEBUG=zerovram. Fixes: 56a171a499c ("radv: don't fast-clear eliminate after resolving a subpass with compute") Signed-off-by: Samuel Pitoiset Reviewed-by: Bas Nieuwenhuizen --- diff --git a/src/amd/vulkan/radv_meta_resolve_cs.c b/src/amd/vulkan/radv_meta_resolve_cs.c index 628208d6356..ede55f6d005 100644 --- a/src/amd/vulkan/radv_meta_resolve_cs.c +++ b/src/amd/vulkan/radv_meta_resolve_cs.c @@ -516,5 +516,8 @@ radv_cmd_buffer_resolve_subpass_cs(struct radv_cmd_buffer *cmd_buffer) &(VkExtent2D) { fb->width, fb->height }); } + cmd_buffer->state.flush_bits |= RADV_CMD_FLAG_CS_PARTIAL_FLUSH | + RADV_CMD_FLAG_INV_VMEM_L1; + radv_meta_restore(&saved_state, cmd_buffer); }