From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754112AbbDUH0R (ORCPT ); Tue, 21 Apr 2015 03:26:17 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:35886 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752772AbbDUH0P (ORCPT ); Tue, 21 Apr 2015 03:26:15 -0400 Date: Tue, 21 Apr 2015 09:26:10 +0200 From: Ingo Molnar To: Namhyung Kim Cc: Arnaldo Carvalho de Melo , Peter Zijlstra , Jiri Olsa , LKML , David Ahern , Taeung Song Subject: Re: [PATCH v2] perf tools: Document --children option in more detail Message-ID: <20150421072610.GB22291@gmail.com> References: <1429533764-11607-1-git-send-email-namhyung@kernel.org> <20150420180411.GA19023@gmail.com> <20150421070108.GE1905@sejong> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150421070108.GE1905@sejong> 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 * Namhyung Kim wrote: > Hi Ingo, > > On Mon, Apr 20, 2015 at 08:04:11PM +0200, Ingo Molnar wrote: > > > > * Namhyung Kim wrote: > > > > > As the --children option changes the output of perf report (and perf > > > top) it sometimes confuses users. Add more words and examples to help > > > understanding of the option's behavior - and how to disable it ;-). > > > > Nice! :-) > > Thanks! :) > > > > > > +++ b/tools/perf/Documentation/overhead.txt > > > > As some people might stumble upon this the old fashioned way, by > > looking around in 'Documentation/', I'm wondering how this file name > > will tell the reader that this is about call chains? (which isn't the > > default recording mode) Maybe name it more explicitly, like > > callchain-overhead.txt? > > OK. But I'd rather name it 'overhead-calculation.txt' to align with > the section name. And 'callchain-overhead' makes me thinking about > the overhead of processing callchains at record or report time. Sure! > > s/perfconfig/.perfconfig > > > > ? > > It seems we can have a system-wide /etc/perfconfig too. How about > 'the perf config file' instead? Yeah. Thanks, Ingo