Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] Problems on usage of markers in combination with	tracepoint probes
Date: Sat, 19 Jun 2010 11:50:54 -0400	[thread overview]
Message-ID: <20100619155054.GB22882@Krystal> (raw)
In-Reply-To: <AANLkTikvutGze72UC6tyuVUDhk3UG5n6QTpA7BJ--thF@mail.gmail.com>

* jerome zh (jeromezhr at gmail.com) wrote:
> Hi Mathieu,
> 
> I did some read on the paper of lttng project, especially your Ph.D thesis.
> I have got some questions:
> 
> 1. Why and when should the marker be used in combination with tracepoint probes?

LTTng is not aware of tracepoints at the moment. So a marker
"declaration" is required to declare the event type and fields. A
tracepoint probe needs to be connected on the tracepoint to write the
event data into the trace stream. See ltt/ltt-type-serializer.c for
details.

> 2. If I want to insert tracepoints in kernel files, such as
> net/ipv4/ip_input.c, can I implement the tracepoints as module?
> Since samples given in samples/tracepoint do NOT show this.

The tracepoint itself must be inserted into the kernel code.

The tracepoint probes, alongside with marker type declaration, must go
into ltt/probes/, which are basically kernel modules.

Thanks,

Mathieu


> 
> -- 
> Regards,
> 
> Jerome
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

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




           reply	other threads:[~2010-06-19 15:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <AANLkTikvutGze72UC6tyuVUDhk3UG5n6QTpA7BJ--thF@mail.gmail.com>]

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=20100619155054.GB22882@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