From: David Ahern <dsahern@gmail.com>
To: William Cohen <wcohen@redhat.com>,
linux-perf-users@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: RFE: More inclusive pid filtering of sched:sched_switch tracepoint events
Date: Wed, 18 Nov 2015 12:18:20 -0700 [thread overview]
Message-ID: <564CCEFC.9030808@gmail.com> (raw)
In-Reply-To: <564CCE9F.4050501@redhat.com>
On 11/18/15 12:16 PM, William Cohen wrote:
> Okay,
>
> As a workaround can use the filtering to cut down some of data being recorded with:
>
> export PID=<process_of_interest>
> sudo perf record -a -e sched:sched_switch --filter "next_pid == $PID || prev_pid == $PID" --
>
> Is the following the correct thread discussing those new sched tracepoints?
>
> https://lkml.org/lkml/2015/6/9/513
>
> -Will
I believe so
next prev parent reply other threads:[~2015-11-18 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 19:01 RFE: More inclusive pid filtering of sched:sched_switch tracepoint events William Cohen
2015-11-18 19:08 ` David Ahern
2015-11-18 19:16 ` William Cohen
2015-11-18 19:18 ` David Ahern [this message]
2015-11-18 20:18 ` Arnaldo Carvalho de Melo
2015-11-19 15:52 ` 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=564CCEFC.9030808@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=wcohen@redhat.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;
as well as URLs for NNTP newsgroup(s).