Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753655AbdF2PXK (ORCPT ); Thu, 29 Jun 2017 11:23:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55226 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753449AbdF2PXA (ORCPT ); Thu, 29 Jun 2017 11:23:00 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 6628AA0214 Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jolsa@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 6628AA0214 Date: Thu, 29 Jun 2017 17:22:52 +0200 From: Jiri Olsa To: "Du, Changbin" Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com, alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] perf sort: only insert overhead && overhead_children when no overhead* field given Message-ID: <20170629152252.GA1463@krava> References: <1496307801-24134-1-git-send-email-changbin.du@intel.com> <1496377320-6114-1-git-send-email-changbin.du@intel.com> <20170626080626.GA3526@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170626080626.GA3526@intel.com> User-Agent: Mutt/1.8.3 (2017-05-23) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Thu, 29 Jun 2017 15:22:54 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2060 Lines: 65 On Mon, Jun 26, 2017 at 04:06:26PM +0800, Du, Changbin wrote: > > Hi, Jiri, > what is the status of this one? I didn't get a response of v2. thanks. > > On Fri, Jun 02, 2017 at 12:22:00PM +0800, changbin.du@intel.com wrote: > > From: Changbin Du > > > > If we always insert 'overhead' and 'overhead_children' as sort keys, > > this make it impossible to sort as overhead (which displayed as Self) > > first.Ths will be a problem if the data is collected with call-graph > > enabled. Then we never can sort the result as self-overhead on this > > data. And sometimes the data is hard to collect. > > > > > perf record -ag > > > perf report -s overhead,sym > > > > Samples: 7K of event 'cycles', Event count (approx.): 865138253 > > Children Self Symbol > > + 26.41% 0.00% [k] verify_cpu > > + 26.37% 0.04% [k] cpu_startup_entry > > + 25.93% 0.27% [k] do_idle > > + 19.88% 0.00% [k] start_secondary > > .... > > > > I intend to sort as 'Self', but actually it sort as 'Children'. > > > > This patch fix this by only insert overhead && overhead_children > > when no overhead* field given. > > > > Signed-off-by: Changbin Du > > --- > > v2: Add the example in commit message. > > > > --- > > tools/perf/util/sort.c | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/tools/perf/util/sort.c b/tools/perf/util/sort.c > > index 5762ae4..69eea3a 100644 > > --- a/tools/perf/util/sort.c > > +++ b/tools/perf/util/sort.c > > @@ -2635,6 +2635,9 @@ static char *setup_overhead(char *keys) > > if (sort__mode == SORT_MODE__DIFF) > > return keys; > > > > + if (strstr(keys, "overhead")) > > + return keys; > > + ah ok, I think it's right.. basically you're forcing precedence of the -s option over the --children option you could have your example working by running: $ perf report -s overhead,sym --no-children please state something like: /* * User already stated overhead within -s option, * do not mangle with that. */ thanks, jirka