From: Oleg Nesterov <oleg@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Josh Stone <jistone@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: Sat, 12 Jan 2013 17:38:40 +0100 [thread overview]
Message-ID: <20130112163840.GA19987@redhat.com> (raw)
In-Reply-To: <20130111093227.GA30043@infradead.org>
On 01/11, 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.
> >
> > In order to actually be usable in module-based tools like SystemTap, the
> > interface needs to be exported. This patch first adds the obvious
> > exports for uprobe_register and uprobe_unregister. Then it also adds
> > one for task_user_regset_view, which is necessary to get the correct
> > state of userspace registers.
>
> Get systemtap into the mainline kernel tree and we can talk.
I can't understand your reply.
Looks like, you do not like the fact that uprobes can be used by the out
of tree modules. Why?
And why, say, kprobe_register() is exported then? Afaics, it does not
have any modular in-kernel user.
As for systemtap in particular. I never used it, and probably you didn't.
But it has a lot of users, and I know many people who find it very useful.
Oleg.
prev parent reply other threads:[~2013-01-12 16:39 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
2013-01-12 16:38 ` Oleg Nesterov [this message]
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=20130112163840.GA19987@redhat.com \
--to=oleg@redhat.com \
--cc=anton@redhat.com \
--cc=hch@infradead.org \
--cc=jistone@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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