public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Shawn Bohrer <shawn.bohrer@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: acme@redhat.com, linux-kernel@vger.kernel.org, paulus@samba.org,
	hpa@zytor.com, mingo@redhat.com, a.p.zijlstra@chello.nl,
	shawn.bohrer@gmail.com, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:perf/core] perf sched: Document missing options
Date: Thu, 2 Dec 2010 11:46:01 GMT	[thread overview]
Message-ID: <tip-1eacc94a66ce347abbf75f223361b21461331383@git.kernel.org> (raw)
In-Reply-To: <1291168642-11402-11-git-send-email-shawn.bohrer@gmail.com>

Commit-ID:  1eacc94a66ce347abbf75f223361b21461331383
Gitweb:     http://git.kernel.org/tip/1eacc94a66ce347abbf75f223361b21461331383
Author:     Shawn Bohrer <shawn.bohrer@gmail.com>
AuthorDate: Tue, 30 Nov 2010 19:57:18 -0600
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Wed, 1 Dec 2010 18:22:48 -0200

perf sched: Document missing options

Cc: Ingo Molnar <mingo@elte.hu>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <1291168642-11402-11-git-send-email-shawn.bohrer@gmail.com>
Signed-off-by: Shawn Bohrer <shawn.bohrer@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/perf/Documentation/perf-sched.txt |   18 ++++++++++++++++--
 1 files changed, 16 insertions(+), 2 deletions(-)

diff --git a/tools/perf/Documentation/perf-sched.txt b/tools/perf/Documentation/perf-sched.txt
index 8417644..46822d5 100644
--- a/tools/perf/Documentation/perf-sched.txt
+++ b/tools/perf/Documentation/perf-sched.txt
@@ -8,11 +8,11 @@ perf-sched - Tool to trace/measure scheduler properties (latencies)
 SYNOPSIS
 --------
 [verse]
-'perf sched' {record|latency|replay|trace}
+'perf sched' {record|latency|map|replay|trace}
 
 DESCRIPTION
 -----------
-There are four variants of perf sched:
+There are five variants of perf sched:
 
   'perf sched record <command>' to record the scheduling events
   of an arbitrary workload.
@@ -30,8 +30,22 @@ There are four variants of perf sched:
   of the workload as it occurred when it was recorded - and can repeat
   it a number of times, measuring its performance.)
 
+  'perf sched map' to print a textual context-switching outline of
+  workload captured via perf sched record.  Columns stand for
+  individual CPUs, and the two-letter shortcuts stand for tasks that
+  are running on a CPU. A '*' denotes the CPU that had the event, and
+  a dot signals an idle CPU.
+
 OPTIONS
 -------
+-i::
+--input=<file>::
+        Input file name. (default: perf.data)
+
+-v::
+--verbose::
+        Be more verbose. (show symbol address, etc)
+
 -D::
 --dump-raw-trace=::
         Display verbose dump of the sched data.

  reply	other threads:[~2010-12-02 11:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01  1:57 [PATCH 00/14] perf documentation updates Shawn Bohrer
2010-12-01  1:57 ` [PATCH 01/14] perf: Document missing annotate options Shawn Bohrer
2010-12-02 11:42   ` [tip:perf/core] perf annotate: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 02/14] perf: Document missing buildid-list options Shawn Bohrer
2010-12-02 11:43   ` [tip:perf/core] perf buildid-list: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 03/14] perf: fix diff displacement and modules options short flag Shawn Bohrer
2010-12-02 11:43   ` [tip:perf/core] perf diff: Fix " tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 04/14] perf: Document missing diff options Shawn Bohrer
2010-12-02 11:43   ` [tip:perf/core] perf diff: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 05/14] perf: Document missing kvm options Shawn Bohrer
2010-12-02 11:44   ` [tip:perf/core] perf kvm: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 06/14] perf: Document missing lock options Shawn Bohrer
2010-12-02 11:44   ` [tip:perf/core] perf lock: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 07/14] perf: Fix spelling mistake in probe documentation Shawn Bohrer
2010-12-01  8:22   ` Masami Hiramatsu
2010-12-02 11:44   ` [tip:perf/core] perf probe: Fix spelling mistake in documentation tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 08/14] perf: Document missing record options Shawn Bohrer
2010-12-02 11:45   ` [tip:perf/core] perf record: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 09/14] perf: Document missing report options Shawn Bohrer
2010-12-02 11:45   ` [tip:perf/core] perf report: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 10/14] perf: Document missing sched options Shawn Bohrer
2010-12-02 11:46   ` tip-bot for Shawn Bohrer [this message]
2010-12-01  1:57 ` [PATCH 11/14] perf: Document missing stat options Shawn Bohrer
2010-12-02 11:47   ` [tip:perf/core] perf stat: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 12/14] perf: Fix spelling mistake in test documentation Shawn Bohrer
2010-12-02 11:47   ` [tip:perf/core] perf test: Fix spelling mistake in documentation tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 13/14] perf: Document missing top options Shawn Bohrer
2010-12-02 11:46   ` [tip:perf/core] perf top: Document missing options tip-bot for Shawn Bohrer
2010-12-01  1:57 ` [PATCH 14/14] perf: Document missing trace options Shawn Bohrer
2010-12-02 11:46   ` [tip:perf/core] perf trace: Document missing options tip-bot for Shawn Bohrer

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=tip-1eacc94a66ce347abbf75f223361b21461331383@git.kernel.org \
    --to=shawn.bohrer@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=tglx@linutronix.de \
    /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