From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932175AbcAHMyq (ORCPT ); Fri, 8 Jan 2016 07:54:46 -0500 Received: from mail.kernel.org ([198.145.29.136]:40586 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754719AbcAHMyp (ORCPT ); Fri, 8 Jan 2016 07:54:45 -0500 Date: Fri, 8 Jan 2016 09:54:41 -0300 From: Arnaldo Carvalho de Melo To: Ingo Molnar Cc: Namhyung Kim , Peter Zijlstra , Jiri Olsa , LKML , David Ahern , Stephane Eranian , Andi Kleen , Masami Hiramatsu , Wang Nan Subject: Re: [RFC/PATCH v3] perf report: Show random usage tip on the help line Message-ID: <20160108125441.GE19314@kernel.org> References: <1452166913-27046-1-git-send-email-namhyung@kernel.org> <20160108075705.GA10894@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160108075705.GA10894@gmail.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Fri, Jan 08, 2016 at 08:57:05AM +0100, Ingo Molnar escreveu: > > * 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. > > > +++ b/tools/perf/Documentation/tips.txt > > @@ -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 [ ] > > +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 > > +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 > > +Use parent filter to see specific call path: perf report -p > > +listing interested events using substring match: perf list > > +To see list of saved events and attributes: perf evlist -v > > +Use --symfs if your symbol files are in non-standard location > > +To see callchains in a more compact form: perf report -g folded > > Very nice! > > Acked-by: Ingo Molnar > > On top of this, what do you think about only doing a single tip per day, the 'tip > of the day'? That would have two effects: > > - people who know all this already see this less > > - people who don't know all this will perhaps be more attentive, because a tip > for every report is more likely to get ignored. > > This could be done via a flag in ~/.perf/ or so. > > Another suggestion: shouldn't the tips be tool specific, i.e. shouldn't there be a > tip-report.txt, tip-record.txt, etc. set of files? Yeah, we could have per tool tip files, but then sometimes to use a feature in 'report' we have to first use some magic combination on the 'record' command line. Anyway, I think I'll apply Namhyung's latest, the one in this message, and get the basic stuff in, we then go on improving on it. - Arnaldo