From mboxrd@z Thu Jan  1 00:00:00 1970
From: david.goulet@polymtl.ca (David Goulet)
Date: Wed, 24 Nov 2010 15:43:46 -0500
Subject: [ltt-dev] RFC LTTv TextDump
In-Reply-To: <4CED6372.7050203@polymtl.ca>
References: <4CEAD092.8020604@polymtl.ca>
	<20101123182653.GA17097@Krystal>	<4CEC182E.5020805@polymtl.ca>
	<4CED6372.7050203@polymtl.ca>
Message-ID: <4CED7902.3020504@polymtl.ca>

On 10-11-24 02:11 PM, Michel Dagenais 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.
>
> The problem is having the full path, a short "id" when interleaved
> events are there would be useful (something about hostname and CPU)

Yep exactly. Just to make it easy to read and easy to refer.

I've also though of a small thing we could add is the time offset in 
nsec (or sec..) between two events.

[...]
event 1 (+4)
event 2 (+7)
[...]

So that way we know *very* quickly what time it took from event 1 to 
event 2 which is 7. Considering a UST trace, this would be of great use!!

We only need someone to do it now :)

David
>
> myhost p1
> yourhost p1
> myhost p1
> myhost p2
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev

-- 
David Goulet
LTTng project, DORSAL Lab.

PGP/GPG : 1024D/16BD8563
BE3C 672B 9331 9796 291A  14C6 4AF7 C14B 16BD 8563