From: Mike Blumenkrantz Date: Tue, 28 Feb 2023 21:05:08 +0000 (-0500) Subject: zink: propagate valid_buffer_range when replacing buffer storage X-Git-Tag: upstream/23.3.3~12058 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a4b1ae1f03c422957cb16a6c57cec5e9f90eab95;p=platform%2Fupstream%2Fmesa.git zink: propagate valid_buffer_range when replacing buffer storage this is otherwise unreliable cc: mesa-stable Part-of: --- diff --git a/src/gallium/drivers/zink/zink_context.c b/src/gallium/drivers/zink/zink_context.c index 1faeca11..021fa0a 100644 --- a/src/gallium/drivers/zink/zink_context.c +++ b/src/gallium/drivers/zink/zink_context.c @@ -5008,6 +5008,7 @@ zink_context_replace_buffer_storage(struct pipe_context *pctx, struct pipe_resou zink_batch_reference_resource(&ctx->batch, d); /* don't be too creative */ zink_resource_object_reference(screen, &d->obj, s->obj); + d->valid_buffer_range = s->valid_buffer_range; /* force counter buffer reset */ d->so_valid = false; if (num_rebinds && rebind_buffer(ctx, d, rebind_mask, num_rebinds) < num_rebinds)