From: Oleg Nesterov <oleg@redhat.com>
To: Josh Stone <jistone@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Anton Arapov <anton@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] uprobes: pre-filtering
Date: Thu, 24 Jan 2013 18:23:40 +0100 [thread overview]
Message-ID: <20130124172340.GA15868@redhat.com> (raw)
In-Reply-To: <510169EA.3070506@redhat.com>
On 01/24, Josh Stone wrote:
>
> On 01/24/2013 07:40 AM, Oleg Nesterov wrote:
> > I'll try to implement the pid-base filtering at least for
> > tracing/uprobe_events, but this needs a time. Not only I am not familiar
> > with this code, I am not sure how this interface should actually look.
> > And I agree, perf should be able to use it somehow, perhaps at least
> > to allow to probe a single task/mm.
>
> Even without changing perf's interface, it already has constraints for
> its child processes (versus --all-cpus) or for specific pid/tid/uid.
> Pre-filtering could help enforce and optimize those constraints.
This is what I meant. The question is how can I do this.
Oleg.
prev parent reply other threads:[~2013-01-24 17:24 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
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 [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=20130124172340.GA15868@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@elte.hu \
--cc=mingo@kernel.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