All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Yuanhan Liu <yuanhan.liu@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add aub debug support for kernel
Date: Tue, 02 Nov 2010 10:02:14 +0000	[thread overview]
Message-ID: <849307$a7if4n@azsmga001.ch.intel.com> (raw)
In-Reply-To: <1288689096-23230-1-git-send-email-yuanhan.liu@intel.com>

On Tue,  2 Nov 2010 17:11:36 +0800, Yuanhan Liu <yuanhan.liu@intel.com> wrote:
> The AUB file is a file format used by Intel's internal simulation
> and other validation tools. The content of an aub file is a subset
> collection of all the data needed by GPU.
> 
> Here now just collects the data that are going to be written into
> register, since the others data like ring buffer, buffer objects
> are dumped at user space by libdrm.
> 
> The currentl implementation: hooks the I915_WRITEx macro. The basic
> idea is write down all the reg offset and reg val before writing
> them to register.

This part looks possible to achieve just using tracepoints (and replace
the current debug printk in the process). The advantage of that is we
can then tap into a low overhead tracing mechanism with a *ringbuffer*!
;-) It will require a bit of userspace scripting to do the .aub format
conversion.

I presume the plan will be to include batchbuffer+auxiliary buffer
contents as well in order to capture the complete temporal sequence for
debugging+replay?

Being able to trace the register writes using ftrace is good... In fact we
can remove our own printks and just use mmiotrace. So is it possible to
post-process mmiotrace into .aub?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2010-11-02 10:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02  9:11 [PATCH] drm/i915: Add aub debug support for kernel Yuanhan Liu
2010-11-02 10:02 ` Chris Wilson [this message]
2010-11-02 14:55   ` Liu Aleaxander
2010-11-04  3:44     ` Liu, Yuanhan
2010-11-04  3:51       ` Liu, Yuanhan
2010-11-04  9:30       ` Chris Wilson
2010-11-05 16:43         ` Liu Aleaxander
2010-11-05 17:11           ` Chris Wilson
2010-11-05 17:39             ` Liu Aleaxander
2010-11-07 14:08             ` Liu Aleaxander
2010-11-07 14:23               ` Chris Wilson
2010-11-07 15:04                 ` Liu Aleaxander
2010-11-07 15:33                   ` Chris Wilson
2010-11-07 15:48                     ` Liu Aleaxander
2010-11-07 16:03                     ` Chris Wilson
2010-11-08  9:23                       ` Yuanhan Liu
2010-11-08  9:55                         ` Chris Wilson
2010-11-09  1:55                           ` 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='849307$a7if4n@azsmga001.ch.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=yuanhan.liu@intel.com \
    /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.