From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] RFC LTTv TextDump
Date: Tue, 23 Nov 2010 15:15:24 -0500 [thread overview]
Message-ID: <20101123201524.GA29834@Krystal> (raw)
In-Reply-To: <4CEC182E.5020805@polymtl.ca>
* 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
next prev parent reply other threads:[~2010-11-23 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 20:20 David Goulet
2010-11-22 20:52 ` Alexandre Montplaisir
2010-11-23 18:26 ` Mathieu Desnoyers
2010-11-23 19:38 ` Alexandre Montplaisir
2010-11-23 20:15 ` Mathieu Desnoyers [this message]
2010-11-24 19:11 ` Michel Dagenais
2010-11-24 20:43 ` David Goulet
2010-11-24 22:49 ` Julien Desfossez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101123201524.GA29834@Krystal \
--to=compudj@krystal.dyndns.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox