It reads @ writes the DB cache, and we haven't flushed dst caches yet,
so DB cache may be stale. Also the user might be shader read (and probably is),
so also flush after.
Signed-off-by: Bas Nieuwenhuizen <ba...@google.com>
CC: <mesa-sta...@lists.freedesktop.org>
Fixes: f4e499ec791 ("radv: add initial non-conformant radv vulkan driver")
---
src/amd/vulkan/radv_cmd_buffer.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/amd/vulkan/radv_cmd_buffer.c b/src/amd/vulkan/radv_cmd_buffer.c
index d3397a0e000..1b13ae7bc64 100644
--- a/src/amd/vulkan/radv_cmd_buffer.c
+++ b/src/amd/vulkan/radv_cmd_buffer.c
@@ -2771,7 +2771,13 @@ static void radv_handle_depth_image_transition(struct
radv_cmd_buffer *cmd_buffe
local_range.baseMipLevel = 0;
local_range.levelCount = 1;
+ cmd_buffer->state.flush_bits |= RADV_CMD_FLAG_FLUSH_AND_INV_DB |
+
RADV_CMD_FLAG_FLUSH_AND_INV_DB_META;
+
radv_decompress_depth_image_inplace(cmd_buffer, image,
&local_range);
+
+ cmd_buffer->state.flush_bits |= RADV_CMD_FLAG_FLUSH_AND_INV_DB |
+
RADV_CMD_FLAG_FLUSH_AND_INV_DB_META;
}
}
--
2.12.1
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
