lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 7 Jan 2016 17:47:53 +0100 From: Andi Kleen <andi@...stfloor.org> To: Namhyung Kim <namhyung@...nel.org> Cc: Arnaldo Carvalho de Melo <acme@...nel.org>, Ingo Molnar <mingo@...nel.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Jiri Olsa <jolsa@...nel.org>, LKML <linux-kernel@...r.kernel.org>, David Ahern <dsahern@...il.com>, Stephane Eranian <eranian@...gle.com>, Andi Kleen <andi@...stfloor.org>, Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>, Wang Nan <wangnan0@...wei.com> Subject: Re: [RFC/PATCH v2] perf report: Show random usage tip on the help line On Thu, Jan 07, 2016 at 04:46:22PM +0900, Namhyung Kim wrote: > Currently perf report only shows a help message "For a higher level > overview, try: perf report --sort comm,dso" unconditionally (even if > the sort keys were used). Add more help tips and show randomly. > > Load tips from ${prefix}/share/doc/perf-tip/tips.txt file. It would be better to compile them in in at build time from the documentation file. Often perf is not installed, and if people don't install they never see the tips. > @@ -0,0 +1,14 @@ > +For a higher level overview, try: perf report --sort comm,dso > +Group related events with: perf record -e '{cycles,instructions}:S' > +Compare performance results with: perf diff [<old file> <new file>] > +Boolean options have negative forms like: perf report --no-children > +Customize output of perf script with: perf script -F event,ip,sym > +Generate a script for your data: perf script -g <lang> > +Save output of perf stat using: perf stat record > +Create archive of data to see it on other machine: perf archive > +Search options using a keyword: perf report -h <keyword> > +Use parent filter to see specific call path: perf report -p <regex> > +listing interested events using substring match: perf list <keyword> > +To see list of saved events and attributes: perf evlist -v > +Use --symfs <dir> if your symbol files are in non-standard location > +To see callchains in a more compact form: perf report -g folded What happened to my tips? -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists