Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: dgoulet@efficios.com (David Goulet)
Subject: [lttng-dev] [lttng-modules PATCH] Add uprobes support
Date: Mon, 14 Jan 2013 14:54:11 -0500	[thread overview]
Message-ID: <50F46263.9000807@efficios.com> (raw)
In-Reply-To: <20130114195104.GA11211@Krystal>

+1

Especially because Uprobe is in mainline since 3.5, would be nice to
support it before it gets in 3.8+ ...

Cheers!
David

Mathieu Desnoyers:
> * Yannick Brosseau (yannick.brosseau at gmail.com) wrote:
>> On 2013-01-14 13:05, Josh Stone wrote:
>>> On 01/13/2013 06:40 PM, Yannick Brosseau wrote:
>>>> +	ret = uprobe_register(event->u.uprobe.inode,
>>>> +			event->u.uprobe.offset,
>>>> +			&event->u.uprobe.up_consumer);
>>>> +	uprobe_unregister(event->u.uprobe.inode,
>>>> +			event->u.uprobe.offset,
>>>> +			&event->u.uprobe.up_consumer);
>>> I'm guessing that you're using a Fedora kernel? :)
>> Oh, you're right... I did not realize that the vanilla kernel did not
>> contains those export.
>>>
>>> These functions are not yet exported upstream, but coincidentally I just
>>> posted a patch for that a few days ago:
>>>
>>>   https://patchwork.kernel.org/patch/1962891/
>>>   https://lkml.org/lkml/2013/1/13/118
>>>
>>> If there's any more complaint about this, maybe you can chime in to
>>> advocate for lttng's needs too.
>>>
>> Ok, I'll weight in if necessary.
> 
> Yes, we should be able to help out if needed.
> 
> Meanwhile, we could use kallsyms to lookup these symbols and use them,
> as we already do in a couple of header under wrappers/ in lttng-modules.
> 
> Thanks,
> 
> Mathieu
> 



  reply	other threads:[~2013-01-14 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  2:40 Yannick Brosseau
2013-01-14 18:05 ` Josh Stone
2013-01-14 18:18   ` Yannick Brosseau
2013-01-14 19:51     ` Mathieu Desnoyers
2013-01-14 19:54       ` David Goulet [this message]
2013-01-15 16:19 ` 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=50F46263.9000807@efficios.com \
    --to=dgoulet@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