From: jerome.stadelmann@heig-vd.ch (Jérôme Stadelmann)
Subject: [ltt-dev] Traces data alignment
Date: Fri, 20 Mar 2009 08:16:39 +0100 [thread overview]
Message-ID: <200903200816.39240.jerome.stadelmann@heig-vd.ch> (raw)
In-Reply-To: <20090319170001.GA27344@Krystal>
On jeudi 19 mars 2009 18:00:01 Mathieu Desnoyers wrote:
> * J?r?me Stadelmann (jerome.stadelmann at heig-vd.ch) wrote:
> > Hi everybody,
> >
> > I'm working on a LTTng traces parser and I'm a little bit blocked on the alignment. Can someone please explain how and where it is coded ?
>
> The lttv lib "ltttraceread" should do that for you.
> > What are the roles of the alignment defined in the traces header and the one defined in the metadata file in the core_marker_id ?
> >
>
> They tell that a specific tracefile content is aligned or not, and if
> the content of a given event is aligned or not. You should really have
> at least a look at the ltt lib traceread reference implementation.
Thank you. This library helped me a lot. I see that there is an up to 2 byte alignment in the core marker id event definition. Is there the only special case ?
I've searched the uses of the ltt_align function. Are there other functions to look for ?
Jerome
> Mathieu
>
> > Regards,
> > Jerome
> >
> > _______________________________________________
> > ltt-dev mailing list
> > ltt-dev at lists.casi.polymtl.ca
> > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> >
>
next prev parent reply other threads:[~2009-03-20 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 15:06 Jérôme Stadelmann
2009-03-19 17:00 ` Mathieu Desnoyers
2009-03-20 7:16 ` Jérôme Stadelmann [this message]
2009-03-20 14:53 ` Mathieu Desnoyers
2009-03-23 7:03 ` Jérôme Stadelmann
2009-03-24 8:34 ` Jérôme Stadelmann
2009-03-24 13:11 ` Mathieu Desnoyers
2009-03-25 6:16 ` Jérôme Stadelmann
2009-03-25 7:05 ` Mathieu Desnoyers
2009-03-26 6:41 ` Jérôme Stadelmann
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=200903200816.39240.jerome.stadelmann@heig-vd.ch \
--to=jerome.stadelmann@heig-vd.ch \
/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