From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
"Wangnan (F)" <wangnan0@huawei.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Stephane Eranian <eranian@google.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [RFC/PATCH] perf report: Show random usage tip on the help line
Date: Tue, 5 Jan 2016 22:51:26 -0300 [thread overview]
Message-ID: <20160106015126.GC6620@kernel.org> (raw)
In-Reply-To: <20160105233753.GB18895@sejong>
Em Wed, Jan 06, 2016 at 08:37:53AM +0900, Namhyung Kim escreveu:
> On Tue, Jan 05, 2016 at 09:52:46PM +0100, Andi Kleen wrote:
> > > Btw, does anyone have some tips to add? :)
> > Use perf script to show individual samples
> > Use perf report --percent-limit 5 to only show entires above 5%
> > Use perf record -b -g / perf report --branch-history to show branch events
> > Use perf record -b / perf report to show branch mispredictions
> > Use perf report -M intel to show Intel style assembler
> > Use perf report --sort srcfile to sort by source file
> > Use perf report --sort symbol,srcline to sort by source line
> > Use perf record -e '{cycles,cache-misses}:S' / perf report --group to associate events
> We should enable --group by default if recorded data file has groups IMHO.
> Arnaldo, could you please take this?
> https://lkml.org/lkml/2015/11/29/76
Sure, I thought I had merged that already, even noticed that yesterday,
when testing some stuff... Will do tomorrow.
> > Use perf mem record / perf mem report for memory address profiling
> > Use perf stat -I 1000 to count events in intervals
> > Use perf stat -I 1000 -x, to count events and output as CSV
> > Use perf timechart record / report to generate high level time line
> > Use perf probe --add kfunc / perf record -e kfunc to trace a custom trace point
> Thanks for sharing!
> > You may also want to adapt some of Brendan's one liners:
> > http://www.brendangregg.com/perf.html
> Will take a look.
Yeah, that is another source, maybe Brendan can put those together in a
brendan.tips.txt that we could put in the /usr/lib/perf/tips/ directory?
;-) :-)
- Arnaldo
next prev parent reply other threads:[~2016-01-06 1:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 5:36 [RFC/PATCH] perf report: Show random usage tip on the help line Namhyung Kim
2016-01-05 6:32 ` Wangnan (F)
2016-01-05 10:43 ` Namhyung Kim
2016-01-05 16:40 ` Arnaldo Carvalho de Melo
2016-01-05 19:19 ` Namhyung Kim
2016-01-05 20:55 ` Arnaldo Carvalho de Melo
2016-01-05 20:59 ` Andi Kleen
2016-01-05 23:29 ` Namhyung Kim
2016-01-06 1:49 ` Arnaldo Carvalho de Melo
2016-01-05 20:52 ` Andi Kleen
2016-01-05 23:37 ` Namhyung Kim
2016-01-06 1:51 ` Arnaldo Carvalho de Melo [this message]
2016-01-08 15:41 ` Arnaldo Carvalho de Melo
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=20160106015126.GC6620@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.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;
as well as URLs for NNTP newsgroup(s).