| 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
| ||
|
Message-ID: <20160708145555.GB17466@gmail.com> Date: Fri, 8 Jul 2016 16:55:55 +0200 From: Ingo Molnar <mingo@...nel.org> To: Peter Zijlstra <peterz@...radead.org> Cc: acme@...nel.org, linux-kernel@...r.kernel.org, andi@...stfloor.org, eranian@...gle.com, jolsa@...nel.org, torvalds@...ux-foundation.org, davidcc@...gle.com, alexander.shishkin@...ux.intel.com, namhyung@...nel.org, kan.liang@...el.com, khandual@...ux.vnet.ibm.com Subject: Re: [RFC][PATCH 7/7] perf/annotate: Add branch stack / basic block information * Peter Zijlstra <peterz@...radead.org> wrote: > $ perf record --branch-filter u,any -e cycles:p ./branches 27 > $ perf annotate branches Btw., I'd really like to use this feature all the time, so could we please simplify this somewhat via a subcommand, via something like: perf record branches ./branches 27 or if 'record' subcommands are not possible anymore: perf record --branches ./branches 27 and in this case 'perf annotate' should automatically pick up the fact that the perf.data was done with --branches - i.e. the highlighting should be automagic. I.e. the only thing a user has to remember to use all this is a single '--branches' option to perf record - instead of a complex sequence for perf record and another sequence for perf annotate. It would also be nice to have 'perf top --branches', with the built-in annotation showing the highlighted branch heat map information and highlighting. Thanks, Ingo
Powered by blists - more mailing lists