From: Oleg Nesterov <oleg@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>, Anton Arapov <anton@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Josh Stone <jistone@redhat.com>,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Steven Rostedt <rostedt@goodmis.org>,
Suzuki Poulose <suzuki@in.ibm.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [GIT PULL] uprobes: pre-filtering
Date: Fri, 25 Jan 2013 17:17:28 +0100 [thread overview]
Message-ID: <20130125161728.GA11630@redhat.com> (raw)
In-Reply-To: <20130125075437.GB21036@gmail.com>
On 01/25, Ingo Molnar wrote:
>
> * Srikar Dronamraju <srikar@linux.vnet.ibm.com> wrote:
>
> > The other alternative is to extend the current abi and pass
> > the prefilter option. Should we extend the abi for userspace
> > tracing is obviously debatable.
>
> That's the obvious path to go - why add something to the kernel
> if user-space cannot make use of it?
This is what I am going to (try to) do, but I am not sure if this makes
sense...
For the start, can't we teach 'uprobe_events' file to accept, say,
'p file:0x1234 pid=1 other-opts'
for the start? This looks simple enough, and I after looked into tools/perf
it seems that perf can be changed too.
What do you think?
Then we can extend 'pid=' option to accept the list of pids, perhaps.
In the long term we probably need uprobes/pid_filter or something like this,
it should allow to add/del pid dynamically. I really do not know.
Oleg.
next prev parent reply other threads:[~2013-01-25 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 18:59 [GIT PULL] uprobes: pre-filtering Oleg Nesterov
2013-01-24 12:17 ` Ingo Molnar
2013-01-24 12:28 ` Anton Arapov
2013-01-24 12:30 ` Ingo Molnar
2013-01-24 15:40 ` Oleg Nesterov
2013-01-24 15:41 ` Ingo Molnar
2013-01-24 17:06 ` Oleg Nesterov
2013-01-25 6:46 ` Srikar Dronamraju
2013-01-25 7:54 ` Ingo Molnar
2013-01-25 16:17 ` Oleg Nesterov [this message]
2013-01-25 18:46 ` Ingo Molnar
2013-01-25 19:34 ` Oleg Nesterov
2013-01-28 12:19 ` Srikar Dronamraju
2013-01-28 16:04 ` Oleg Nesterov
2013-01-25 11:23 ` Masami Hiramatsu
2013-01-24 17:05 ` Josh Stone
2013-01-24 17:23 ` 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=20130125161728.GA11630@redhat.com \
--to=oleg@redhat.com \
--cc=ananth@in.ibm.com \
--cc=anton@redhat.com \
--cc=hch@infradead.org \
--cc=jistone@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=suzuki@in.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 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.