From: William Cohen <wcohen@redhat.com>
To: linux-perf-users@vger.kernel.org
Subject: RFE: More inclusive pid filtering of sched:sched_switch tracepoint events
Date: Wed, 18 Nov 2015 14:01:13 -0500 [thread overview]
Message-ID: <564CCAF9.3070805@redhat.com> (raw)
Hi,
I was experimenting with the sched:sched_switch tracepoint to look at
the time that a process spend off the processor. As a really simple
experiment record data with:
$ sudo perf record -e sched:sched_switch -- du
Then examine the data with:
$ sudo perf script
The output only shows the sched:sched_switch when the process is moved
off the processor. However, there is no data showing when the process is
scheduled back onto the processor:
du 20960 [007] 339893.429394: sched:sched_switch: du:20960 [120] R ==> kworker/7:0:16805 [120]
du 20960 [007] 339893.429411: sched:sched_switch: du:20960 [120] R ==> kworker/7:0:16805 [120]
du 20960 [007] 339893.429544: sched:sched_switch: du:20960 [120] R ==> kworker/7:0:16805 [120]
du 20960 [007] 339893.429556: sched:sched_switch: du:20960 [120] R ==> kworker/7:0:16805 [120]
du 20960 [007] 339893.429561: sched:sched_switch: du:20960 [120] R ==> kworker/7:0:16805 [120]
du 20960 [007] 339893.429567: sched:sched_switch: du:20960 [120] R ==> kworker/7:0:16805 [120]
du 20960 [007] 339893.430150: sched:sched_switch: du:20960 [120] R ==> kworker/7:0:16805 [120]
Would it be possible to make perf's process filtering more inclusive so
that output also includes sched:sched_switch tracepoints for pid that
are also being scheduled onto the processor? The alternative of
recording all sched:sched_switch events system-wide and filtering out
all the unwanted pid's is undesirable.
-Will
next reply other threads:[~2015-11-18 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 19:01 William Cohen [this message]
2015-11-18 19:08 ` RFE: More inclusive pid filtering of sched:sched_switch tracepoint events David Ahern
2015-11-18 19:16 ` William Cohen
2015-11-18 19:18 ` David Ahern
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=564CCAF9.3070805@redhat.com \
--to=wcohen@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
/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).