All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Kenneth Graunke <kenneth@whitecape.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] intel: Add .aub file output support.
Date: Fri, 9 Mar 2012 11:53:06 +0800	[thread overview]
Message-ID: <20120309035306.GW17001@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <4F590513.9000005@whitecape.org>

On Thu, Mar 08, 2012 at 11:14:27AM -0800, Kenneth Graunke wrote:
> On 03/07/2012 06:51 PM, Yuanhan Liu wrote:
> >On Wed, Mar 07, 2012 at 11:21:07AM -0800, Eric Anholt wrote:
> >>From: Kenneth Graunke<kenneth@whitecape.org>
> >>
> >>This will allow the driver to capture all of its execution state to a
> >>file for later debugging.  intel_gpu_dump is limited in that it only
> >>captures batchbuffers, and Mesa's captures, while more complete, still
> >>capture only a portion of the state involved in execution.
> >>
> >>It also enables us to load traces in our internal simulator.
> >>
> >>Signed-off-by: Eric Anholt<eric@anholt.net>
> >>Signed-off-by: Yuanhan Liu<yuanhan.liu@linux.intel.com>
> >>Signed-off-by: Kenneth Graunke<kenneth@whitecape.org>
> >>---
> >>  intel/Makefile.am        |    1 +
> >>  intel/intel_aub.h        |  123 ++++++++++++++++++
> >>  intel/intel_bufmgr.h     |   14 ++
> >>  intel/intel_bufmgr_gem.c |  315 ++++++++++++++++++++++++++++++++++++++++++++++
> >>  4 files changed, 453 insertions(+), 0 deletions(-)
> >>  create mode 100644 intel/intel_aub.h
> >>
[snip]...
> >>+	/* MI_FLUSH enable */
> >>+	if (bufmgr_gem->gen>= 6) {
> >>+		aub_out(bufmgr_gem, CMD_AUB_TRACE_HEADER_BLOCK | (5 - 2));
> >>+		aub_out(bufmgr_gem, AUB_TRACE_OP_MMIO_WRITE);
> >>+		aub_out(bufmgr_gem, 0);
> >>+		aub_out(bufmgr_gem, 0x209c);  /* reg addr */
> >>+		aub_out(bufmgr_gem, 0x04);    /* Length in byte */
> >>+		aub_out(bufmgr_gem, ((1<<  12)<<  16) | (1<<  12));
> >>+	}
> >
> >Zhenyu and me came to an agreement that it's the driver side to do the
> >MI_FLUSH enable stuff. Since using MI_FLUSH is deprecated, and if you still
> >use it, it is your job to set up the MI_FLUSH enable bit.
> 
> Oh...yeah, we should definitely drop that.
> 
> >>+}
> >>+
> >>+/**
> >>   * Initializes the GEM buffer manager, which uses the kernel to allocate, map,
> >>   * and manage map buffer objections.
> >>   *
> >>--
> >>1.7.9.1
> 
> Otherwise,
> Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
> 
> Please set yourself as the author, though - I just squashed this and
> fixed up a few minor things.

Eric wrote the original code, I just made it work. But, of course, feel
free to set it if you think it's a need ;)

Thanks,
Yuanhan Liu

  reply	other threads:[~2012-03-09  3:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 19:21 [PATCH 1/2] intel: Add support for overriding the PCI ID via an environment variable Eric Anholt
2012-03-07 19:21 ` [PATCH 2/2] intel: Add .aub file output support Eric Anholt
2012-03-08  2:51   ` Yuanhan Liu
2012-03-08 19:14     ` Kenneth Graunke
2012-03-09  3:53       ` Yuanhan Liu [this message]
2012-03-08  9:13   ` Paul Menzel
2012-03-08 18:43     ` Eric Anholt
2012-03-08  2:35 ` [PATCH 1/2] intel: Add support for overriding the PCI ID via an environment variable Yuanhan Liu

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=20120309035306.GW17001@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kenneth@whitecape.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.