Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Human read-writeable format for CTF traces
Date: Mon, 3 Feb 2014 16:19:50 +0000 (UTC)	[thread overview]
Message-ID: <1219414962.18229.1391444390292.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <2093535948.9680292.1391443217617.JavaMail.root@polymtl.ca>

----- Original Message -----
> From: "Michel Dagenais" <michel.dagenais@polymtl.ca>
> To: "Mathieu Desnoyers" <mathieu.desnoyers at efficios.com>
> Cc: lttng-dev at lists.lttng.org, "Genevi?ve Bastien" <gbastien+lttng at versatic.net>
> Sent: Monday, February 3, 2014 11:00:17 AM
> Subject: Re: [lttng-dev] Human read-writeable format for CTF traces
> 
> 
> > I would expect that the ctf writer API recently added to babeltrace
> > (currently in master branch), along with the Python bindings that cover
> > trace read and write APIs, should allow you to implement things like:
> > 
> > - A plugin to read a CTF trace, and output it in an intermediate format
> >   to facilitate edits (e.g. XML as you propose),
> > - A plugin to read this XML format and output a CTF trace.
> 
> Yes, this would indeed be extremely helpful, in XML and/or JSON.
> 
> > You could also generate the XML trace completely by hand if you like, and
> > then convert it to CTF with the second plugin I'm relating to above.
> 
> The likely scenario is to add a few events by hand.
> 
> > Another possibility is that the XML description also allows
> > describing what the trace contains at a slightly higher level. For
> > instance, if you
> > have a periodic event happening for a certain amount of time, it would
> > be described in XML, and then "generated" by the XML-to-CTF
> > converter.
> 
> Do we want to describe this in XML or in Python? We could have "CTF" to
> "Python statements" generating XML. Then we could add loops by hand. We
> could also have CTF to XML, with hooks to merge Python generated events.

I very much like this idea. Indeed, with a CTF-to-Python-statements converter,
we can easily tweak the resulting python script to add events, modify events,
and even use loops and re-use functions. This would be extremely useful for
unit-testing the state system, and would allow re-use (import) of patterns
more easily than with XML descriptions.

Thanks,

Mathieu

> 
> In addition, TMF may also want to offer similar functionality, an XML dump of
> events and an XML events reader. Indeed, TMF supports a few formats other
> than CTF.
> 

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



  reply	other threads:[~2014-02-03 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 14:59 Geneviève Bastien
2014-02-03 15:12 ` Mathieu Desnoyers
2014-02-03 16:00   ` Michel Dagenais
2014-02-03 16:19     ` Mathieu Desnoyers [this message]
2014-02-03 17:05     ` Geneviève Bastien
2014-02-03 17:16       ` Mathieu Desnoyers
2014-02-03 17:20         ` Geneviève Bastien
2014-02-04 16:19           ` Jérémie Galarneau
2014-02-04 17:35             ` Geneviève Bastien
2014-02-04 17:46               ` Jérémie Galarneau
2014-02-04 18:50                 ` Geneviève Bastien
2014-02-03 15:28 ` Matthew Khouzam

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=1219414962.18229.1391444390292.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    /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