1. 17 Sep, 2017 1 commit
  2. 16 Sep, 2017 2 commits
  3. 13 Sep, 2017 1 commit
    • Kenneth Graunke's avatar
      i965: Add an INTEL_DEBUG=submit option for printing batch statistics. · edfd8d42
      Kenneth Graunke authored
      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's avatarChris Wilson <chris@chris-wilson.co.uk>
  4. 12 Sep, 2017 7 commits
  5. 09 Sep, 2017 1 commit
    • Roland Scheidegger's avatar
      llvmpipe: enable PIPE_CAP_QUERY_PIPELINE_STATISTICS · 772f4753
      Roland Scheidegger authored
      This was implemented since forever, but not enabled.
      It passes all piglit tests except one, arb_pipeline_statistics_query-frag.
      The reason is that the test (for drawing a 10x10 rect) expects between
      100 and 150 pixel shader invocations. But since llvmpipe counts this with
      4x4 granularity (and due to the rect being 2 tris) we end up with 224
      invocations. I believe however what llvmpipe is doing violates neither the
      spirit nor the letter of the spec (our fragment shader granularity really
      is 4x4 pixels, albeit we will bail out early on 2x2 or 4x2 (the latter
      if AVX is available) granularity), the spec allows to count additional
      invocations due to implementation reasons.
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      Reviewed-by: Jose Fonseca's avatarJose Fonseca <jfonseca@vmware.com>
  6. 08 Sep, 2017 3 commits
  7. 07 Sep, 2017 1 commit
  8. 06 Sep, 2017 3 commits
  9. 04 Sep, 2017 3 commits
  10. 28 Aug, 2017 3 commits
  11. 25 Aug, 2017 4 commits
  12. 22 Aug, 2017 7 commits
  13. 21 Aug, 2017 3 commits
  14. 17 Aug, 2017 1 commit