drivers should be maintaining a local copy of the rp info, and this
provides a consistent way to reset that info if a renderpass is ended
early
Acked-by: Marek Olšák <marek.olsak@amd.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21800>
info->zsbuf_fbfetch;
}
+/* if a driver ends a renderpass early for some reason,
+ * this function can be called to reset any stored renderpass info
+ * to a "safe" state that will avoid data loss on framebuffer attachments
+ *
+ * note: ending a renderpass early if invalidate hints are applied will
+ * result in data loss
+ */
+static inline void
+tc_renderpass_info_reset(struct tc_renderpass_info *info)
+{
+ info->data32[0] = 0;
+ info->cbuf_load = BITFIELD_MASK(8);
+ info->zsbuf_clear_partial = true;
+ info->has_draw = true;
+ info->has_query_ends = true;
+}
+
struct tc_batch {
struct threaded_context *tc;
#if !defined(NDEBUG) && TC_DEBUG >= 1
{
if (!ctx->batch.in_rp)
return;
- if (zink_screen(ctx->base.screen)->driver_workarounds.track_renderpasses && !ctx->blitting) {
- ctx->dynamic_fb.tc_info.data = 0;
- ctx->dynamic_fb.tc_info.cbuf_load = BITFIELD_MASK(8);
- ctx->dynamic_fb.tc_info.zsbuf_clear_partial = true;
- ctx->dynamic_fb.tc_info.has_draw = true;
- ctx->dynamic_fb.tc_info.has_query_ends = true;
- }
+ if (zink_screen(ctx->base.screen)->driver_workarounds.track_renderpasses && !ctx->blitting)
+ tc_renderpass_info_reset(&ctx->dynamic_fb.tc_info);
zink_batch_no_rp_safe(ctx);
}