Re: [Intel-gfx] [PATCH] drm/i915: Add aub debug support for kernel

2010-11-02 Thread Liu Aleaxander
Hi Chris, On Tue, Nov 2, 2010 at 6:02 PM, Chris Wilson wrote: > On Tue,  2 Nov 2010 17:11:36 +0800, Yuanhan Liu 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 b

Re: [Intel-gfx] [PATCH] drm/i915: Add aub debug support for kernel

2010-11-05 Thread Liu Aleaxander
On Thu, Nov 4, 2010 at 5:30 PM, Chris Wilson wrote: > On Thu, 4 Nov 2010 11:44:39 +0800, "Liu, Yuanhan" > wrote: >> >> On Tue, 2010-11-02 at 22:55 +0800, Liu Aleaxander wrote: >> > >> > > Being able to trace the register writes using ftrace is

Re: [Intel-gfx] [PATCH] drm/i915: Add aub debug support for kernel

2010-11-05 Thread Liu Aleaxander
On Sat, Nov 6, 2010 at 1:11 AM, Chris Wilson wrote: > Right. If we want to ask the user to gather some debug info, it > essentially has to be from within X and be as simple as run > 'intel-gpu-trace myapp'. Some notes here: let's me try to make it clear this time. As I had said, we can easily get

Re: [Intel-gfx] [PATCH] drm/i915: Add aub debug support for kernel

2010-11-07 Thread Liu Aleaxander
On 11/6/10, Chris Wilson wrote: > > Right. If we want to ask the user to gather some debug info, it > essentially has to be from within X and be as simple as run > 'intel-gpu-trace myapp'. Using ftrace is the simplest way to achieve > that. Having to rmmod i915.ko rules out mmiotrace as a viable c

Re: [Intel-gfx] [PATCH] drm/i915: Add aub debug support for kernel

2010-11-07 Thread Liu Aleaxander
On Sun, Nov 7, 2010 at 10:23 PM, Chris Wilson wrote: > On Sun, 7 Nov 2010 22:08:00 +0800, Liu Aleaxander > wrote: >> I wrote a new patch(no post-processing yet). >> Chris, is this what you want? > > Yes, that looks good. Thanks:) >The compiler should be able to d

Re: [Intel-gfx] [PATCH] drm/i915: Add aub debug support for kernel

2010-11-07 Thread Liu Aleaxander
On Sun, Nov 7, 2010 at 11:33 PM, Chris Wilson wrote: > > The hacky approach is a module parameter (i915.trace_load=1) that we parse > in i915_init() and enable the trace points manually. I remember this being > possible, once upon a time... Yes, I will check if it is possible tomorrow(night here).