From c19aedcf1a83c70a999b963dfbc0bce47a189600 Mon Sep 17 00:00:00 2001 From: Gurchetan Singh Date: Fri, 11 Jan 2019 17:49:59 -0800 Subject: [PATCH] virgl: don't mark unclean after a flush The guest memory is still clean until host GL touches it, which we should track elsewhere. Reviewed-by: Gert Wollny --- src/gallium/drivers/virgl/virgl_buffer.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/gallium/drivers/virgl/virgl_buffer.c b/src/gallium/drivers/virgl/virgl_buffer.c index 6762011e5c6..25fb992ef1f 100644 --- a/src/gallium/drivers/virgl/virgl_buffer.c +++ b/src/gallium/drivers/virgl/virgl_buffer.c @@ -120,7 +120,6 @@ static void virgl_buffer_transfer_flush_region(struct pipe_context *ctx, * We'll end up flushing 25 --> 70. */ util_range_add(&trans->range, box->x, box->x + box->width); - vbuf->clean[0] = FALSE; } static const struct u_resource_vtbl virgl_buffer_vtbl = -- 2.30.2