From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753546AbcCAMca (ORCPT ); Tue, 1 Mar 2016 07:32:30 -0500 Received: from mx1.redhat.com ([209.132.183.28]:43551 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753447AbcCAMc2 (ORCPT ); Tue, 1 Mar 2016 07:32:28 -0500 Date: Tue, 1 Mar 2016 13:32:25 +0100 From: Jiri Olsa To: Andi Kleen Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org, Andi Kleen Subject: Re: [PATCH 5/7] perf, tools, stat: Implement --metric-only mode Message-ID: <20160301123225.GF622@krava.redhat.com> References: <1456785386-19481-1-git-send-email-andi@firstfloor.org> <1456785386-19481-6-git-send-email-andi@firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1456785386-19481-6-git-send-email-andi@firstfloor.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 01 Mar 2016 12:32:28 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 29, 2016 at 02:36:24PM -0800, Andi Kleen wrote: > From: Andi Kleen > > Add a new mode to only print metrics. Sometimes we don't care about > the raw values, just want the computed metrics. This allows more > compact printing, so with -I each sample is only a single line. > This also allows easier plotting and processing with other tools. > > The main target is with using --topdown, but it also works with > -T and standard perf stat. A few metrics are not supported. > > To avoiding having to hardcode all the metrics in the code it uses > a two pass approach: first compute dummy metrics and only > print the headers in the print_metric callback. Then use the callback > to print the actual values. > > There are some additional changes > in the stat printout code to handle all metrics being on a single line. > > One issue is that the column code doesn't know in advance what events > are not supported by the CPU, and it would be hard to find out > as this could change based on dynamic conditions. That causes > empty columns in some cases. > > The output can be fairly wide, often you may need more than 80 columns. > > Example: > > % perf stat -a -I 1000 --metric-only > 1.001452803 frontend cycles idle insn per cycle stalled cycles per insn branch-misses of all branches where does 'frontend' collumn come from? can't see it in the code or get it in output.. thanks, jirka > 1.001452803 158.91% 0.66 2.39 2.92% > 2.002192321 180.63% 0.76 2.08 2.96% > 3.003088282 150.59% 0.62 2.57 2.84% > 4.004369835 196.20% 0.98 1.62 3.79% > 5.005227314 231.98% 0.84 1.90 4.71% > SNIP