diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2014-02-12 10:34:34 +0000 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2014-02-12 10:34:34 +0000 |
| commit | fb69bd16a30cd0449fa9bb603dacd001e777b5bb (patch) | |
| tree | 1e80268d9dc0e4aea402bf2526b9a05d33050edd /src | |
| parent | 77f8d9ca84342b256de1e118edfd14ddae4d593f (diff) | |
sna/gen5: Use the DBG option ALWAYS_FLUSH to force a full flush
When flushing between operations, we can choose between doing a full
flush to memory, or just a pipeline flush. For debugging it is better to
do the full flush to rule out cache effects.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'src')
| -rw-r--r-- | src/sna/gen5_render.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/sna/gen5_render.c b/src/sna/gen5_render.c index a9db697a..a89d31a3 100644 --- a/src/sna/gen5_render.c +++ b/src/sna/gen5_render.c @@ -1049,7 +1049,7 @@ gen5_emit_state(struct sna *sna, } gen5_emit_vertex_elements(sna, op); - if (kgem_bo_is_dirty(op->src.bo) || kgem_bo_is_dirty(op->mask.bo)) { + if (ALWAYS_FLUSH || kgem_bo_is_dirty(op->src.bo) || kgem_bo_is_dirty(op->mask.bo)) { DBG(("%s: flushing dirty (%d, %d)\n", __FUNCTION__, kgem_bo_is_dirty(op->src.bo), kgem_bo_is_dirty(op->mask.bo))); @@ -1058,7 +1058,7 @@ gen5_emit_state(struct sna *sna, kgem_bo_mark_dirty(op->dst.bo); flush = false; } - if (flush || ALWAYS_FLUSH) { + if (flush) { DBG(("%s: forcing flush\n", __FUNCTION__)); gen5_emit_pipe_flush(sna); } |