intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: intel-gfx@lists.freedesktop.org
Cc: mesa-dev@lists.freedesktop.org, Ben Widawsky <ben@bwidawsk.net>,
	Carl Worth <cworth@cworth.org>,
	dri-devel@lists.freedesktop.org
Subject: [PATCH 00/10] fs debugging: incorporated Chris' feedback
Date: Sun, 17 Jul 2011 16:25:38 -0700	[thread overview]
Message-ID: <1310945148-6777-1-git-send-email-ben@bwidawsk.net> (raw)

This is the revised patch series for fragment shader debugging.

There is no major change, though of interest are:
  * forcewaked acts more like a daemon
  * forcewaked isn't needed for debugging only there for sample
  * i915 detection is now done by stating i915_forcewake_user_lock
  * register range checking fails for gen2/gen3

drm:
 intel/Makefile.am   |    3 ++-
 intel/intel_debug.h |   44 ++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 46 insertions(+), 1 deletions(-)

mesa:
 src/mesa/drivers/dri/i965/Makefile           |    1 +
 src/mesa/drivers/dri/i965/brw_context.h      |    6 +
 src/mesa/drivers/dri/i965/brw_eu.c           |    6 +
 src/mesa/drivers/dri/i965/brw_eu.h           |    1 +
 src/mesa/drivers/dri/i965/brw_fs_emit.cpp    |   15 +-
 src/mesa/drivers/dri/i965/brw_misc_state.c   |   12 +-
 src/mesa/drivers/dri/i965/brw_state.h        |    6 +-
 src/mesa/drivers/dri/i965/brw_state_cache.c  |   49 +-
 src/mesa/drivers/dri/i965/brw_state_upload.c |   18 +-
 src/mesa/drivers/dri/i965/brw_wm.c           |   27 +-
 src/mesa/drivers/dri/i965/brw_wm.h           |    2 +
 src/mesa/drivers/dri/i965/brw_wm_debug.c     |  108 +
 src/mesa/drivers/dri/i965/brw_wm_emit.c      |    2 +
 src/mesa/drivers/dri/i965/gen6_wm_sr.c       |   31 +
 src/mesa/drivers/dri/i965/gen_wm_sr.g4a      |32826 ++++++++++++++++++++++++++
 15 files changed, 33087 insertions(+), 23 deletions(-)

intel-gpu-tools:
 configure.ac                             |    1 +
 debugger/Makefile.am                     |   12 +
 debugger/debug_rdata.c                   |  141 +++++++
 debugger/eudb.c                          |  604 ++++++++++++++++++++++++++++++
 debugger/system_routine/Makefile         |   84 ++++
 debugger/system_routine/eviction_macro.c |   48 +++
 debugger/system_routine/pre_cpp.py       |  123 ++++++
 debugger/system_routine/sr.g4a           |  277 ++++++++++++++
 debugger/system_routine/test.g4a         |   64 ++++
 lib/Makefile.am                          |    1 +
 lib/debug.h                              |   92 +++++
 lib/intel_chipset.h                      |    8 +
 lib/intel_gpu_tools.h                    |   27 ++
 lib/intel_mmio.c                         |  162 ++++++++-
 lib/intel_reg.h                          |    4 +
 lib/intel_reg_map.c                      |  178 +++++++++
 tools/Makefile.am                        |    1 +
 tools/forcewaked.c                       |  106 ++++++
 18 files changed, 1932 insertions(+), 1 deletions(-)


Thanks.
Ben

             reply	other threads:[~2011-07-17 23:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17 23:25 Ben Widawsky [this message]
2011-07-17 23:25 ` [PATCH 01/10] intel: shared header for shader debugging Ben Widawsky
2011-07-17 23:25 ` [PATCH 02/10] i965: copy in system routine, reserve extra scratch Ben Widawsky
2011-07-17 23:25 ` [PATCH 03/10] i965: Reserve scratch space for debugger communication Ben Widawsky
2011-07-17 23:25 ` [PATCH 04/10] i965: setup system routine Ben Widawsky
2011-07-18 18:19   ` [Intel-gfx] " Eric Anholt
2011-07-19  4:48     ` Ben Widawsky
2011-07-17 23:25 ` [PATCH 05/10] i965: emit breakpoints Ben Widawsky
2011-07-17 23:25 ` [PATCH 06/10] i965: attach to a listening debugger Ben Widawsky
2011-07-17 23:25 ` [PATCH 07/10] intel-gpu-tools: register range handling for forcewake hooks Ben Widawsky
2011-07-17 23:25 ` [PATCH 08/10] intel-gpu-tools/forcewaked: sample forcewake app Ben Widawsky
2011-07-17 23:25 ` [PATCH 09/10] debugging: add important debug regs Ben Widawsky
2011-07-17 23:25 ` [PATCH 10/10] debugging: shader debugging Ben Widawsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1310945148-6777-1-git-send-email-ben@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=cworth@cworth.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mesa-dev@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).