From: tip-bot for Kim SeonYoung <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, adamas0414@gmail.com, mingo@kernel.org,
linux-kernel@vger.kernel.org, hpa@zytor.com, taeung@kosslab.kr,
namhyung@kernel.org, acme@redhat.com, jolsa@kernel.org,
peterz@infradead.org
Subject: [tip:perf/urgent] perf report/top: Add a tip about source line numbers with overhead
Date: Thu, 6 Oct 2016 15:43:33 -0700 [thread overview]
Message-ID: <tip-8649b6434ebc184e632a510c4121899481409c15@git.kernel.org> (raw)
In-Reply-To: <1475194602-5596-1-git-send-email-adamas0414@gmail.com>
Commit-ID: 8649b6434ebc184e632a510c4121899481409c15
Gitweb: http://git.kernel.org/tip/8649b6434ebc184e632a510c4121899481409c15
Author: Kim SeonYoung <adamas0414@gmail.com>
AuthorDate: Thu, 29 Sep 2016 17:16:42 -0700
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Wed, 5 Oct 2016 19:47:55 -0300
perf report/top: Add a tip about source line numbers with overhead
There is a existing tip as below.
If you have debuginfo enabled, try: perf report -s sym,srcline
However this tip only describe a condition to use --sort sym,scrline
options. So there is lack of explanation in the tip. I think that it
would be better to add a tip that exactly explains the feature of --sort
srcline.
Signed-off-by: Seonyoung Kim <adamas0414@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Taeung Song <taeung@kosslab.kr>
Link: http://lkml.kernel.org/r/1475194602-5596-1-git-send-email-adamas0414@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/Documentation/tips.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt
index 5950b5a..b031124 100644
--- a/tools/perf/Documentation/tips.txt
+++ b/tools/perf/Documentation/tips.txt
@@ -28,3 +28,4 @@ To change sampling frequency to 100 Hz: perf record -F 100
See assembly instructions with percentage: perf annotate <symbol>
If you prefer Intel style assembly, try: perf annotate -M intel
For hierarchical output, try: perf report --hierarchy
+Order by the overhead of source file name and line number: perf report -s srcline
prev parent reply other threads:[~2016-10-06 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 0:16 [PATCH v2] perf report: " Kim SeonYoung
2016-10-06 22:43 ` tip-bot for Kim SeonYoung [this message]
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-8649b6434ebc184e632a510c4121899481409c15@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=adamas0414@gmail.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=peterz@infradead.org \
--cc=taeung@kosslab.kr \
--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
all inboxes | Powered by JetHome®