From mboxrd@z Thu Jan  1 00:00:00 1970
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Date: Tue, 23 Nov 2010 13:26:54 -0500
Subject: [ltt-dev] RFC LTTv TextDump
In-Reply-To: <4CEAD092.8020604@polymtl.ca>
References: <4CEAD092.8020604@polymtl.ca>
Message-ID: <20101123182653.GA17097@Krystal>

* David Goulet (david.goulet at polymtl.ca) wrote:
> Hi everyone,
>
> I propose here, only an idea, to create a lttv plugin for "human  
> readable" text dump. There is too much information in the current  
> textdump and it's not quite useful showing a lot of cryptic symbol and  
> sec.nsec timestamp.
>
> From this (currently) :
>
> ust.event: 336310.284597315  
> (/data/dave/.usttraces/raoul-20101122150921506792809/12821_5542468726404202641/ust_6), 
> 0, 0, , , 0, 0x0, MODE_UNKNOWN { n = 42, b = 1 }
>
> I propose that this plugin output something like that :
>
> [%H:%M:%S nsec] <channel>.<event_name> : <PAYLOAD>
>
> (here is the example below)
>
> [93:25:10 284597315] ust.event : { n = 42, b = 1 }
> (we could maybe cut down 93 hours to 3 days)
>
> and having the first output of the trace being the information like :
>
> Trace set contains 1 traces
> <PATH_OF_TRACE>
> Buffer size, basic stats.
>
> For "user friendly" output, it will be way more useful.
>
> Anyone wants to jump in that kind of "small" project :)

Note that the textdump can output content coming from multiple traces,
where having the trace name in the output for each event becomes
convenient.

But when we show only one trace, it would not be needed. I'm just saying
we should not remove it entirely in every cases, because it is sometimes
needed.

Thanks,

Mathieu


-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com