On Sat, Aug 1, 2015 at 2:06 AM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > On Fri, Jul 31, 2015 at 10:53:26AM -0700, krh@xxxxxxxxxxxxx wrote: >> From: Kristian Høgsberg Kristensen <kristian.h.kristensen@xxxxxxxxx> >> >> We now have a separate tool for this in intel-gpu-tools and we don't >> need to clutter up libdrm with this feature. We leave the entry points >> in there to avoid breaking API/ABI. > > A quick mention of the replacement would be a useful pointer. > > To use the new aub dumping tool install intel-gpu-tools and run > > $ intel_aubdump --output=the.aub -- glxgears > > See intel_aubdump for further details. > > Yes, with the new tool that is more general than the aub writer here, we > no longer need the clutter in libdrm. (intel_aubdump looks really nice > btw, though I would like an "igt trace" :)) > > Reviewed-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> Thanks for taking a look. I realized I have to leave intel_aub.h in since it's an installed header and used by mesa. I added a pointer and example to the deprecation and commit messages. By igt trace, do you mean something that captures and decodes all ioctls? That sounds useful too, could be a separate mode or even separate tool. Kristian > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
