Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: piotr.romaniuk@elesoftrom.com.pl (Piotr Romaniuk)
Subject: [lttng-dev] Difference between markers, tracepoints and trace_events
Date: Wed, 04 Apr 2012 10:23:15 +0200	[thread overview]
Message-ID: <4F7C04F3.9070305@elesoftrom.com.pl> (raw)
In-Reply-To: <4F4224E4.6080108@elesoftrom.com.pl>

Hi,

I would like to use tracing of execution in my kernel driver.
I saw in LTTng documentation and source code that there are several methods:
1) markers,
2) tracepoints,
3) trace_events.
I saw that programming interface for usage each of these item is little 
different.
What is the difference between these methods? Are they equivalent from 
conceptual point of view?
I successfuly used markers and observed logged entries in LTTTV, but 
have no success with trace_events.

I use following versions:
- Linux kernel 2.6.33.2 (+ rt13 patch)
- lttng kernel patch 0.212
- lttctl 0.87
- ltttv 0.12.36

Regards,
Piotr Romaniuk




       reply	other threads:[~2012-04-04  8:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F4224E4.6080108@elesoftrom.com.pl>
2012-04-04  8:23 ` Piotr Romaniuk [this message]
2012-04-10 13:58   ` Ettore Del Negro
2012-04-10 15:28   ` Mathieu Desnoyers

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=4F7C04F3.9070305@elesoftrom.com.pl \
    --to=piotr.romaniuk@elesoftrom.com.pl \
    /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