public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: "Pavey, Nicholas" <npavey@akamai.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Using perf to locate source of context switches
Date: Wed, 04 Dec 2013 11:47:48 -0700	[thread overview]
Message-ID: <529F78D4.10905@gmail.com> (raw)
In-Reply-To: <CEC4D35C.A428%npavey@akamai.com>

On 12/4/13, 10:42 AM, Pavey, Nicholas wrote:
> NB: I have also used 'perf record -e cs -g -a -- sleep 2', while the

Add -c 1 to capture *all* context switch events.

perf script will show each event. perf report provides a histogram summary.

I have a time-history command for analyzing scheduling events. It is not 
yet in upstream code. You can try the code in this branch:

https://github.com/dsahern/linux/tree/perf-sched-timehist-3.11

Or download this version (requires Arnaldo's tree):
https://lkml.org/lkml/2013/11/18/555

David

  reply	other threads:[~2013-12-04 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 17:42 Using perf to locate source of context switches Pavey, Nicholas
2013-12-04 18:47 ` David Ahern [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-04 17:35 Pavey, Nicholas

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=529F78D4.10905@gmail.com \
    --to=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npavey@akamai.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