From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Liang, Kan" <kan.liang@intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Andi Kleen <ak@linux.intel.com>,
jacob.w.shin@gmail.com, standby24x7@gmail.com,
Li Zefan <lizefan@huawei.com>,
yunlong.song@huawei.com, Steven Rostedt <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
pi3orama@163.com
Subject: Re: [PATCH v2] perf tools: Allow passing perf's own pid to '--filter'
Date: Tue, 7 Jul 2015 10:27:13 -0300 [thread overview]
Message-ID: <20150707132713.GB3326@kernel.org> (raw)
In-Reply-To: <CAM9d7cg3wL1iVVaOr2jGG60QXO-huvv-mV9tauU2om0nEH0sHw@mail.gmail.com>
Em Tue, Jul 07, 2015 at 09:33:02PM +0900, Namhyung Kim escreveu:
> On Tue, Jul 7, 2015 at 12:38 PM, Wang Nan <wangnan0@huawei.com> wrote:
> > This patch introduces '$PERFPID' placeholder to perf's filter. Now
> > user is allowed to do the above work with:
> > # perf record -e ... --filter='common_pid != $PERFPID' -a sleep 10
> Instead, what about adding an option to do the same thing, like
> --exclude-perf or something?
Good idea, that would be more compact, yes.
- Arnaldo
next prev parent reply other threads:[~2015-07-07 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 3:38 [PATCH v2] perf tools: Allow passing perf's own pid to '--filter' Wang Nan
2015-07-07 12:33 ` Namhyung Kim
2015-07-07 13:27 ` Arnaldo Carvalho de Melo [this message]
2015-07-07 14:19 ` Wangnan (F)
2015-07-07 14:38 ` Arnaldo Carvalho de Melo
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=20150707132713.GB3326@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=jacob.w.shin@gmail.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pi3orama@163.com \
--cc=rostedt@goodmis.org \
--cc=standby24x7@gmail.com \
--cc=wangnan0@huawei.com \
--cc=yunlong.song@huawei.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.