debug: Don't always flush the batch when emitting a debugging flush
I incorrectly changed the logic in 285f286 and caused the batch to
always be flushed when debugging, instead of merely inserting a MI_FLUSH
between operations.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
This commit is contained in:
parent
c10850c63f
commit
a8ea20100d
|
|
@ -71,7 +71,10 @@ void i830_debug_flush(ScrnInfoPtr scrn)
|
|||
{
|
||||
intel_screen_private *intel = intel_get_screen_private(scrn);
|
||||
|
||||
if (intel->debug_flush & (DEBUG_FLUSH_BATCHES | DEBUG_FLUSH_CACHES))
|
||||
if (intel->debug_flush & DEBUG_FLUSH_CACHES)
|
||||
intel_batch_pipelined_flush(scrn);
|
||||
|
||||
if (intel->debug_flush & DEBUG_FLUSH_BATCHES)
|
||||
intel_batch_flush(scrn, FALSE);
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -128,7 +128,7 @@ void intel_batch_flush(ScrnInfoPtr scrn, Bool flush)
|
|||
|
||||
assert (!intel->in_batch_atomic);
|
||||
|
||||
if (flush || intel->debug_flush & DEBUG_FLUSH_CACHES) {
|
||||
if (flush) {
|
||||
int flags = MI_WRITE_DIRTY_STATE | MI_INVALIDATE_MAP_CACHE;
|
||||
|
||||
if (IS_I965G(intel))
|
||||
|
|
|
|||
Loading…
Reference in New Issue