Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] Babeltrace API plan
Date: Fri, 4 Nov 2011 15:45:27 -0400	[thread overview]
Message-ID: <20111104194527.GA32677@Krystal> (raw)

Hi!

After a few people asking questions about the direction I plan to take
regarding the Babeltrace Common Trace Format (CTF) reading API, I think
it's good that I clarify this publicly on the mailing list:

For those interested in using it from external applications:

a) first create your prototype by including the private babeltrace
   headers you need.
b) then, as you do this, you'll find out what you need exported
c) please propose a patch to babeltrace to export what you need 
   through a clean API

I'm not exporting all the headers that are needed to access the
information read by babeltrace yet, because I don't want to expose the
guts of babeltrace to applications (which would be a problem if we want
to change the implementation). So we really need to come up with a clean
API to allow access to the CTF "ir" (intermediate representation) of the
trace.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com




                 reply	other threads:[~2011-11-04 19:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20111104194527.GA32677@Krystal \
    --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