Quoting Kenneth Graunke (2017-09-06 01:09:35) > When a batch is flushed, INTEL_DEBUG=bat prints a message indicating > which part of the code triggered the flushed, 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=flush 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).
Sensible, but do you want INTEL_DEBUG=flush to capture pipecontrol flush/invalidates? INTEL_DEBUG=submit? -Chris _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
