public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Stone <jistone@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: oleg@redhat.com, srikar@linux.vnet.ibm.com, mingo@kernel.org,
	peterz@infradead.org, anton@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uprobes: Add exports for module use
Date: Fri, 11 Jan 2013 13:42:33 -0800	[thread overview]
Message-ID: <50F08749.2020306@redhat.com> (raw)
In-Reply-To: <20130111093227.GA30043@infradead.org>

Hi Christoph,

On 01/11/2013 01:32 AM, Christoph Hellwig wrote:
> On Thu, Jan 10, 2013 at 03:01:46PM -0800, Josh Stone wrote:
>> The original pull message for uprobes (commit 654443e2) noted:
>>
>>   This tree includes uprobes support in 'perf probe' - but SystemTap
>>   (and other tools) can take advantage of user probe points as well.

I believe this quoted line already signaled the intent that SystemTap
use should be allowed.

> Get systemtap into the mainline kernel tree and we can talk.

This is unlikely to ever happen, nor do I think it's necessarily
appropriate.  For instance, we are also developing an alternate mode of
operation that uses Dyninst instead of kernel modules.  We're keeping
both modes for their different trade-offs, but in general the tool's
relationship with the kernel is somewhat weaker now.

Thanks,
Josh


  reply	other threads:[~2013-01-11 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 23:01 [PATCH] uprobes: Add exports for module use Josh Stone
2013-01-11  9:32 ` Christoph Hellwig
2013-01-11 21:42   ` Josh Stone [this message]
2013-01-12 16:38   ` Oleg Nesterov

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=50F08749.2020306@redhat.com \
    --to=jistone@redhat.com \
    --cc=anton@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=srikar@linux.vnet.ibm.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