All of lore.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Taeung Song <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, namhyung@kernel.org,
	linux-kernel@vger.kernel.org, treeze.taeung@gmail.com,
	hpa@zytor.com, jolsa@kernel.org, acme@redhat.com,
	mingo@kernel.org
Subject: [tip:perf/core] perf config: Document variables for 'report' section in man page
Date: Tue, 9 Feb 2016 04:11:15 -0800	[thread overview]
Message-ID: <tip-806cb95bb6cb25105b37d971d9916105898cb6fe@git.kernel.org> (raw)
In-Reply-To: <1454577913-16401-4-git-send-email-treeze.taeung@gmail.com>

Commit-ID:  806cb95bb6cb25105b37d971d9916105898cb6fe
Gitweb:     http://git.kernel.org/tip/806cb95bb6cb25105b37d971d9916105898cb6fe
Author:     Taeung Song <treeze.taeung@gmail.com>
AuthorDate: Thu, 4 Feb 2016 18:25:08 +0900
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Thu, 4 Feb 2016 11:44:25 -0300

perf config: Document variables for 'report' section in man page

Explain 'report' section's variables:

  'percent-limit', 'queue-size' and 'children'.

Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Link: http://lkml.kernel.org/r/1454577913-16401-4-git-send-email-treeze.taeung@gmail.com
[ Fix some grammar issues, add some more info ]
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/perf/Documentation/perf-config.txt | 36 ++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/tools/perf/Documentation/perf-config.txt b/tools/perf/Documentation/perf-config.txt
index 42310ae..f38f46f 100644
--- a/tools/perf/Documentation/perf-config.txt
+++ b/tools/perf/Documentation/perf-config.txt
@@ -369,6 +369,42 @@ call-graph.*::
 		This is a maximum number of lines of callchain printed for a single
 		histogram entry. Default is 0 which means no limitation.
 
+report.*::
+	report.percent-limit::
+		This one is mostly the same as call-graph.threshold but works for
+		histogram entries. Entries having an overhead lower than this
+		percentage will not be printed. Default is '0'. If percent-limit
+		is '10', only entries which have more than 10% of overhead will be
+		printed.
+
+	report.queue-size::
+		This option sets up the maximum allocation size of the internal
+		event queue for ordering events. Default is 0, meaning no limit.
+
+	report.children::
+		'Children' means functions called from another function.
+		If this option is true, 'perf report' cumulates callchains of children
+		and show (accumulated) total overhead as well as 'Self' overhead.
+		Please refer to the 'perf report' manual. The default is 'true'.
+
+	report.group::
+		This option is to show event group information together.
+		Example output with this turned on, notice that there is one column
+		per event in the group, ref-cycles and cycles:
+
+		# group: {ref-cycles,cycles}
+		# ========
+		#
+		# Samples: 7K of event 'anon group { ref-cycles, cycles }'
+		# Event count (approx.): 6876107743
+		#
+		#         Overhead  Command      Shared Object               Symbol
+		# ................  .......  .................  ...................
+		#
+		    99.84%  99.76%  noploop  noploop            [.] main
+		     0.07%   0.00%  noploop  ld-2.15.so         [.] strcmp
+		     0.03%   0.00%  noploop  [kernel.kallsyms]  [k] timerqueue_del
+
 SEE ALSO
 --------
 linkperf:perf[1]

  reply	other threads:[~2016-02-09 12:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04  9:25 [PATCH 0/8] perf config: Document config variables in man page Taeung Song
2016-02-04  9:25 ` [PATCH 1/8] perf config: Document 'ui.show-headers' variable " Taeung Song
2016-02-09 12:10   ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04  9:25 ` [PATCH 2/8] perf config: Document variables for 'call-graph' section " Taeung Song
2016-02-09 12:10   ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04  9:25 ` [PATCH 3/8] perf config: Document variables for 'report' " Taeung Song
2016-02-09 12:11   ` tip-bot for Taeung Song [this message]
2016-02-04  9:25 ` [PATCH 4/8] perf config: Document 'top.children' variable " Taeung Song
2016-02-09 12:11   ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04  9:25 ` [PATCH 5/8] perf config: Document 'man.viewer' " Taeung Song
2016-02-09 12:12   ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04  9:25 ` [PATCH 6/8] perf config: Document 'pager.<subcommand>' variables " Taeung Song
2016-02-09 12:12   ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04  9:25 ` [PATCH 7/8] perf config: Document 'kmem.default' variable " Taeung Song
2016-02-09 12:12   ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04  9:25 ` [PATCH 8/8] perf config: Document 'record.build-id' " Taeung Song
2016-02-09 12:13   ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04 14:49 ` [PATCH 0/8] perf config: Document config variables " Arnaldo Carvalho de Melo
2016-02-05 10:41   ` Taeung Song
2016-02-05 11:03   ` Taeung Song
2016-02-05 13:04     ` Namhyung Kim
2016-02-05 13:39       ` Arnaldo Carvalho de Melo
2016-02-05 13:42         ` Taeung Song
2016-02-05 13:44         ` Namhyung Kim

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-806cb95bb6cb25105b37d971d9916105898cb6fe@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=acme@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=treeze.taeung@gmail.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.