radv: Don't flush the CB before doing a fast clear eliminate.
authorBas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Sun, 5 Mar 2017 16:17:06 +0000 (17:17 +0100)
committerBas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Thu, 9 Mar 2017 01:35:28 +0000 (02:35 +0100)
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 <basni@google.com>
Reviewed-by: Dave Airlie <airlied@redhat.com>
src/amd/vulkan/radv_meta_fast_clear.c

index 8009b287c4db422099415b83c0bd6f30017c79a9..eedd3e15b94f50a8e1795857813be8da4fbdb044 100644 (file)
@@ -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,