This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Using systemtap to look at futexs
- From: Tim Bird <tim dot bird at am dot sony dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: systemtap <systemtap at sourceware dot org>
- Date: Tue, 16 May 2006 15:40:35 -0700
- Subject: Re: Using systemtap to look at futexs
- References: <20060516215615.GF17707@redhat.com> <446A4D7F.5010706@am.sony.com> <20060516222913.GH17707@redhat.com>
Frank Ch. Eigler wrote:
> Hi -
>
> On Tue, May 16, 2006 at 03:09:03PM -0700, Tim Bird wrote:
>
>> [...] Aside from improved ease-of-development, it could be
>> beneficial to have a standardized output format, such that the data
>> could be used with other trace presentation and analysis tools (like
>> lttv from LTT or kd from KFT).
>
> One can write functions in the scripting language to format trace data
> in any reasonable format.
Yes, but my point is that outputting a known, standardized format
(as opposed to "any reasonable format") could have side benefits.
If you're going to write helper functions for the output, a nice
side effect of the regularization of the handling would also be
a regularization of the formatting, with the possibility to make
the data more widely usable.
> (Plus one can write scripting language code
> to perform some of the analysis live that these trace tools do after
> the fact.)
Yes, some. Is there a visualization tool for SystemTap data?
-- Tim
P.S. Sorry, my original comment didn't go to the list because
I forgot to reply-all. I hope it's OK to put the thread back
on-list.
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================