Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTT satus
Date: Wed, 1 Oct 2008 14:37:57 -0400	[thread overview]
Message-ID: <20081001183757.GA18617@Krystal> (raw)
In-Reply-To: <48E3C0F4.3000808@igi.cnr.it>

Hi,

Facilities are gone long ago. They used a XML description for events
which turned into C code using genevent, a C code generator. It was
rather hellish to keep in sync the kernel code with the XML
descriptions.

The markers are an in-kernel API (see include/linux/marker.h and
Documentation/markers.txt) which lets you describe your events in the C
code. The typing is expressed using a format string. It's automatically
saved in the trace at trace start/module load, so you don't have to take
care of such details by yourself : the meta information about events is
automatically exported through the trace.

Mathieu

* barbalace at igi.cnr.it (barbalace at igi.cnr.it) wrote:
> Dear LTT team,
> I'm involved in the activity of using LTTng to trace RTAI. RTAI has an old 
> support of LTT but this is a don't care issue. The problem is that I've not 
> a clear idea of how LTTng work. My basic question is: what is the 
> difference between Facilities and Markers? Are both still in use?
> I'm currently work with probably not a brand new version of LTTng: the last 
> one that patch linux kernel 2.6.19...
>
> Thanks a lot
>
> - Antonio Barbalace
>
> Istituto Gas Ionizzati del CNR
> Consorzio RFX - Associazione EURATOM/ENEA sulla Fusione
> Corso Stati Uniti 4, 35127 Padova - Italy
> mailto:barbalace at igi.cnr.it, http://www.igi.cnr.it
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68




      reply	other threads:[~2008-10-01 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 18:27 barbalace
2008-10-01 18:37 ` Mathieu Desnoyers [this message]

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=20081001183757.GA18617@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