All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Stone <jistone@redhat.com>
To: Christian Babeux <christian.babeux@efficios.com>
Cc: David Smith <dsmith@redhat.com>,
	lttng-dev@lists.lttng.org, systemtap@sourceware.org
Subject: Re: [lttng-dev] Using lttng-ust's libringbuffer outside lttng-ust
Date: Fri, 15 Feb 2013 19:43:55 -0800	[thread overview]
Message-ID: <511F007B.9020701@redhat.com> (raw)
In-Reply-To: <CAGDH53=8kL0oXWZ0Xo73-1EviVbheU0t9fXuzSt05ZCSqVzH_w@mail.gmail.com>

On 02/15/2013 12:36 PM, Christian Babeux wrote:
> With that said, I'm curious about which specific features of Dyninst
> SystemTAP will be using and also do you think that it would be
> possible to integrate Dyninst as an additional instrumentation source
> into lttng-ust?

We're using Dyninst mainly like a pure-userspace form of uprobes, so we
can instrument a process without any direct kernel involvement.  In this
mode, stap is perfectly fine for unprivileged users (on their own
processes), and it can be faster too since it's running instrumentation
directly in-process (versus uprobes' breakpoint trap).  Like uprobes,
these instrumentation points can be anywhere in the process.

And sure, I can definitely see lttng using it for similar reasons.
We've already packaged Dyninst in Fedora, if you'd like to try it out.

Josh

  reply	other threads:[~2013-02-16  3:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 19:56 Using lttng-ust's libringbuffer outside lttng-ust David Smith
2013-02-15 20:36 ` [lttng-dev] " Christian Babeux
2013-02-16  3:43   ` Josh Stone [this message]
2013-02-25 19:07   ` David Smith
2013-02-25 19:07   ` David Smith

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=511F007B.9020701@redhat.com \
    --to=jistone@redhat.com \
    --cc=christian.babeux@efficios.com \
    --cc=dsmith@redhat.com \
    --cc=lttng-dev@lists.lttng.org \
    --cc=systemtap@sourceware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.