From: tip-bot for Andi Kleen <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: ak@linux.intel.com, jolsa@kernel.org, acme@redhat.com,
mingo@kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, hpa@zytor.com
Subject: [tip:perf/urgent] perf tools: Add some new tips describing the new options
Date: Fri, 22 Mar 2019 15:15:52 -0700 [thread overview]
Message-ID: <tip-ca52babe033f2a0a535ce7c814e54a44cead1f15@git.kernel.org> (raw)
In-Reply-To: <20190311144502.15423-9-andi@firstfloor.org>
Commit-ID: ca52babe033f2a0a535ce7c814e54a44cead1f15
Gitweb: https://git.kernel.org/tip/ca52babe033f2a0a535ce7c814e54a44cead1f15
Author: Andi Kleen <ak@linux.intel.com>
AuthorDate: Mon, 11 Mar 2019 07:44:59 -0700
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Mon, 11 Mar 2019 16:33:19 -0300
perf tools: Add some new tips describing the new options
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
Link: http://lkml.kernel.org/r/20190311144502.15423-9-andi@firstfloor.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/Documentation/tips.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt
index 849599f39c5e..869965d629ce 100644
--- a/tools/perf/Documentation/tips.txt
+++ b/tools/perf/Documentation/tips.txt
@@ -15,6 +15,7 @@ To see callchains in a more compact form: perf report -g folded
Show individual samples with: perf script
Limit to show entries above 5% only: perf report --percent-limit 5
Profiling branch (mis)predictions with: perf record -b / perf report
+To show assembler sample contexts use perf record -b / perf script -F +brstackinsn --xed
Treat branches as callchains: perf report --branch-history
To count events in every 1000 msec: perf stat -I 1000
Print event counts in CSV format with: perf stat -x,
@@ -34,3 +35,9 @@ Show current config key-value pairs: perf config --list
Show user configuration overrides: perf config --user --list
To add Node.js USDT(User-Level Statically Defined Tracing): perf buildid-cache --add `which node`
To report cacheline events from previous recording: perf c2c report
+To browse sample contexts use perf report --sample 10 and select in context menu
+To separate samples by time use perf report --sort time,overhead,sym
+To set sample time separation other than 100ms with --sort time use --time-quantum
+Add -I to perf report to sample register values visible in perf report context.
+To show IPC for sampling periods use perf record -e '{cycles,instructions}:S' and then browse context
+To show context switches in perf report sample context add --switch-events to perf record.
next prev parent reply other threads:[~2019-03-22 22:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 14:44 Support sample context in perf report Andi Kleen
2019-03-11 14:44 ` [PATCH v6 01/11] perf tools script: Filter COMM/FORK/.. events by CPU Andi Kleen
2019-03-11 16:58 ` Arnaldo Carvalho de Melo
2019-03-22 22:12 ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2019-03-11 14:44 ` [PATCH v6 02/11] perf tools report: Parse time quantum Andi Kleen
2019-03-11 16:59 ` Arnaldo Carvalho de Melo
2019-03-11 14:44 ` [PATCH v6 03/11] perf tools report: Support time sort key Andi Kleen
2019-03-11 17:04 ` Arnaldo Carvalho de Melo
2019-03-22 22:13 ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2019-03-11 14:44 ` [PATCH v6 04/11] perf tools report: Use less for scripts output Andi Kleen
2019-03-11 17:05 ` Arnaldo Carvalho de Melo
2019-03-11 14:44 ` [PATCH v6 05/11] perf tools report: Support running scripts for current time range Andi Kleen
2019-03-11 17:06 ` Arnaldo Carvalho de Melo
2019-03-22 22:13 ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2019-03-11 14:44 ` [PATCH v6 06/11] perf tools report: Support builtin perf script in scripts menu Andi Kleen
2019-03-11 17:09 ` Arnaldo Carvalho de Melo
2019-03-22 22:14 ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2019-03-11 14:44 ` [PATCH v6 07/11] perf tools report: Implement browsing of individual samples Andi Kleen
2019-03-11 17:24 ` Jiri Olsa
2019-03-11 17:46 ` Andi Kleen
2019-03-11 18:35 ` Arnaldo Carvalho de Melo
2019-03-11 19:04 ` Andi Kleen
2019-03-22 22:15 ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2019-03-11 14:44 ` [PATCH v6 08/11] perf tools: Add some new tips describing the new options Andi Kleen
2019-03-22 22:15 ` tip-bot for Andi Kleen [this message]
2019-03-11 14:45 ` [PATCH v6 09/11] perf tools report: Add custom scripts to script menu Andi Kleen
2019-03-11 18:10 ` Arnaldo Carvalho de Melo
2019-03-11 18:34 ` Andi Kleen
2019-03-11 18:45 ` Arnaldo Carvalho de Melo
2019-03-22 22:17 ` [tip:perf/urgent] " tip-bot for Andi Kleen
2019-03-11 14:45 ` [PATCH v6 10/11] perf tools script: Add array bound checking to list_scripts Andi Kleen
2019-03-11 18:18 ` Arnaldo Carvalho de Melo
2019-03-22 22:16 ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2019-03-11 14:45 ` [PATCH v6 11/11] perf tools ui: Fix ui popup browser for many entries Andi Kleen
2019-03-11 18:17 ` Arnaldo Carvalho de Melo
2019-03-22 22:17 ` [tip:perf/urgent] perf ui browser: Fix ui popup argv " tip-bot for Andi Kleen
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-ca52babe033f2a0a535ce7c814e54a44cead1f15@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.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=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 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.