diff options
| author | Gurchetan Singh <[email protected]> | 2019-01-11 17:49:59 -0800 |
|---|---|---|
| committer | Gert Wollny <[email protected]> | 2019-02-15 11:19:04 +0100 |
| commit | c19aedcf1a83c70a999b963dfbc0bce47a189600 (patch) | |
| tree | 7096670b80125c19a7d1e59ca1669c420f4ba83d | |
| parent | 5b6a2ae987d6d6895d80ce61292e2025cacb5125 (diff) | |
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 <[email protected]>
| -rw-r--r-- | src/gallium/drivers/virgl/virgl_buffer.c | 1 |
1 files changed, 0 insertions, 1 deletions
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 = |