diff options
| author | Kenneth Graunke <[email protected]> | 2017-09-05 15:46:30 -0700 |
|---|---|---|
| committer | Kenneth Graunke <[email protected]> | 2017-09-13 13:52:38 -0700 |
| commit | edfd8d42a9ac870a6ebc5a56fc003f60f86b702c (patch) | |
| tree | 43fa8703c4125e2fc87a7967bee22a5a490b767e /src/mesa | |
| parent | 64d9bd149aa7f5a09f73cae07499577933722fb2 (diff) | |
i965: Add an INTEL_DEBUG=submit option for printing batch statistics.
When a batch is submitted, INTEL_DEBUG=bat prints a message indicating
which part of the code triggered the flush, and some statistics about
the batch/state buffer utilization.
It also decodes the batchbuffer in debug builds...which is so much
output that it drowns out the utilization messages, if that's all you
care about.
INTEL_DEBUG=submit now just does the utilization messages.
INTEL_DEBUG=bat continues to do both (as the message is a good indicator
that we're starting decode of a new batch).
v2: Rename from "flush" to "submit" (suggested by Chris) because we
might want "flush" for PIPE_CONTROL debugging someday.
Reviewed-by: Chris Wilson <[email protected]>
Diffstat (limited to 'src/mesa')
| -rw-r--r-- | src/mesa/drivers/dri/i965/intel_batchbuffer.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mesa/drivers/dri/i965/intel_batchbuffer.c b/src/mesa/drivers/dri/i965/intel_batchbuffer.c index 08d35ace135..515b595bc92 100644 --- a/src/mesa/drivers/dri/i965/intel_batchbuffer.c +++ b/src/mesa/drivers/dri/i965/intel_batchbuffer.c @@ -731,7 +731,7 @@ _intel_batchbuffer_flush_fence(struct brw_context *brw, brw_bo_reference(brw->throttle_batch[0]); } - if (unlikely(INTEL_DEBUG & DEBUG_BATCH)) { + if (unlikely(INTEL_DEBUG & (DEBUG_BATCH | DEBUG_SUBMIT))) { int bytes_for_commands = 4 * USED_BATCH(brw->batch); int bytes_for_state = brw->batch.bo->size - brw->batch.state_batch_offset; int total_bytes = bytes_for_commands + bytes_for_state; |