From: Bas Nieuwenhuizen Date: Sun, 5 Mar 2017 16:17:06 +0000 (+0100) Subject: radv: Don't flush the CB before doing a fast clear eliminate. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=7d6e1a341af6d29110fbc83aa139fedade2851d1;p=mesa.git radv: Don't flush the CB before doing a fast clear eliminate. The only way we write CMASK/DCC compressed textures through shaders is fast clears and CMASK/DCC inits, which have their own flushes. Hence the CB cache is always up to date. Signed-off-by: Bas Nieuwenhuizen Reviewed-by: Dave Airlie --- diff --git a/src/amd/vulkan/radv_meta_fast_clear.c b/src/amd/vulkan/radv_meta_fast_clear.c index 8009b287c4d..eedd3e15b94 100644 --- a/src/amd/vulkan/radv_meta_fast_clear.c +++ b/src/amd/vulkan/radv_meta_fast_clear.c @@ -372,8 +372,6 @@ emit_fast_clear_flush(struct radv_cmd_buffer *cmd_buffer, }, }; - cmd_buffer->state.flush_bits |= (RADV_CMD_FLAG_FLUSH_AND_INV_CB | - RADV_CMD_FLAG_FLUSH_AND_INV_CB_META); radv_cmd_buffer_upload_data(cmd_buffer, sizeof(vertex_data), 16, vertex_data, &offset); struct radv_buffer vertex_buffer = { .device = device,