All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Diego Dompe <ddompe@gmail.com>
Cc: lttng-dev@lists.lttng.org, tiwg@multicore-association.org
Subject: Re: Questions about CTF format
Date: Thu, 2 May 2013 16:27:58 -0400	[thread overview]
Message-ID: <20130502202758.GE15675__20868.9194209457$1367526511$gmane$org@Krystal> (raw)
In-Reply-To: <CAEBwSh8vqVr9LsPPRxx_c9da7M3spcMwrHTkSX+bWE1_UQVXbw@mail.gmail.com>

* Diego Dompe (ddompe@gmail.com) wrote:
> Hi Mathieu,
> 
> Thanks for the help. Here is my list of details:
> 
> - Clocks: the spec doesn't explain properly that timestamps are an offset
> from the base time of the clock they refer to. Since I was using 64bit
> timestamps I somehow assumed that I was using absolute timestamps from the
> epoch (although the spec doesn't says it either).

Not sure if it was there when you wrote your comment, but the CTF spec
currently has:

"The "offset_s" and "offset" fields indicate the offset from POSIX.1
Epoch, 1970-01-01 00:00:00 +0000 (UTC), to the zero of value of the
clock."

> - I saw that the lttng-generated traces for metadata are always a multiple
> of 4k in size (at least the ones I generate for either kernel or user
> space). I can't find where in the spec it mentions requirements regarding
> metadata packet padding. I was generating metadata packets that ended up
> right after my TSDL and eclipse wasn't happy about it (although I didn't
> try babeltrace). Also I found that the lttng-generated traces have a
> "empty" metadata packet after the metadata containing the TSDL, I didn't
> find either any documentation regarding this.

Babeltrace had a limitation on not accepting packets smaller than 4kB
(page size actually), but it is now fixed.

Thanks,

Mathieu

> 
> Regards,
> 
> Diego
> 
> On Thu, Jul 5, 2012 at 8:20 AM, Mathieu Desnoyers <
> mathieu.desnoyers@efficios.com> wrote:
> 
> > * Diego Dompe (ddompe@gmail.com) wrote:
> > > Hi,
> > >
> > > I'm developing a custom tracer for an embedded product that will generate
> > > CTF format. I was able to generate generic traces that can be interpreted
> > > properly with babeltrace (but not with eclipse, I already file a bug for
> > > that), but I found the CTF specification lacking in some aspects (I had
> > to
> > > peek into lttng-generated CTF traces to figure out some details). I was
> > > wondering what is the proper mailing list to clear my questions and
> > provide
> > > feedback on the CTF specification for improvement in the areas where the
> > > documentation is not detailed yet. I don't see any CTF-specific mailing
> > > list, it's OK to discuss it here? Or maybe directly with a developer(s)?
> >
> > Hi Diego,
> >
> > Yes, this mailing list would be the proper place, along maybe with
> > adding the MCA tiwg mailing list in CC, which I'm doing here.
> >
> > Thanks,
> >
> > Mathieu
> >
> > --
> > Mathieu Desnoyers
> > Operating System Efficiency R&D Consultant
> > EfficiOS Inc.
> > http://www.efficios.com
> >

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  parent reply	other threads:[~2013-05-02 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEBwSh_OkCZiWJXQrUO3fnLnka3MfTJpa8z0HqxxVFd7CtPqOg@mail.gmail.com>
2012-07-05 14:20 ` Questions about CTF format Mathieu Desnoyers
     [not found] ` <20120705142052.GA23162@Krystal>
2012-07-05 14:49   ` Diego Dompe
     [not found]   ` <CAEBwSh8vqVr9LsPPRxx_c9da7M3spcMwrHTkSX+bWE1_UQVXbw@mail.gmail.com>
2012-08-31 14:34     ` Matthew Khouzam
2013-05-02 20:27     ` Mathieu Desnoyers [this message]
2012-07-05 14:15 Diego Dompe

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='20130502202758.GE15675__20868.9194209457$1367526511$gmane$org@Krystal' \
    --to=mathieu.desnoyers@efficios.com \
    --cc=ddompe@gmail.com \
    --cc=lttng-dev@lists.lttng.org \
    --cc=tiwg@multicore-association.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.