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>
This commit is contained in:
parent
77f8d9ca84
commit
fb69bd16a3
|
|
@ -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);
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in New Issue