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

* Alexandre Montplaisir (alexandre.montplaisir at polymtl.ca) wrote:
> On 10-11-23 01:26 PM, Mathieu Desnoyers wrote:
>> 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
>>
>>
>
> Yeah, I thought about that just after posting. In that case we could  
> have the complete trace paths at the start in the header of the file,  
> and in the events just a quick fixed-width reference. Something like:
>
>
> Trace 01 : /home/user/traces/.../trace-alpha
> Trace 02 : /tmp/autotrace1
>

We also really need a legend at the top.

Mathieu

> ...
> channel.eventtype, timestamp, 01, 01, 1000, 1000, Event payload { n =  
> 42, b = 2 }
> ...
>
> the numbers representing Trace #1, CPU #1, PID 1000, TGID 1000
>
>
> Alexandre
>

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