From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754988AbdCGKDw (ORCPT ); Tue, 7 Mar 2017 05:03:52 -0500 Received: from mx1.redhat.com ([209.132.183.28]:44122 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754653AbdCGKD0 (ORCPT ); Tue, 7 Mar 2017 05:03:26 -0500 Date: Tue, 7 Mar 2017 11:03:20 +0100 From: Jiri Olsa To: Andi Kleen Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org, Andi Kleen Subject: Re: [PATCH 08/10] perf, tools, stat: Output JSON MetricExpr metric Message-ID: <20170307100320.GD12093@krava> References: <20170301064924.32172-1-andi@firstfloor.org> <20170301064924.32172-9-andi@firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170301064924.32172-9-andi@firstfloor.org> User-Agent: Mutt/1.8.0 (2017-02-23) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 07 Mar 2017 10:03:23 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 28, 2017 at 10:49:22PM -0800, Andi Kleen wrote: > From: Andi Kleen > > Add generic infrastructure to perf stat to output ratios for "MetricExpr" > entries in the event lists. Many events are more useful as ratios > than in raw form, typically some count in relation to total ticks. > > Transfer the MetricExpr information from the alias to the evsel. > > We mark the events that need to be collected for MetricExpr, and also > link the events using them with a pointer. The code is careful > to always prefer the right event in the same group to minimize > multiplexing errors. At the moment only a single relation is supported. > > Then add a rblist to the stat shadow code that remembers stats based > on the cpu and context. > > Then finally update and retrieve and print these values similarly to the > existing hardcoded perf metrics. We use the simple expression parser > added earlier to evaluate the expression. > > Normally we just output the result without further commentary, > but for --metric-only this would lead to empty columns. So for this > case use the original event as description. > > So far there is no attempt to automatically add the MetricExpr event, > if it is missing, however we suggest it to the user. > > $ perf stat -a -I 1000 -e '{unc_p_clockticks,unc_p_freq_max_os_cycles}' > 1.000228813 800,139,950 unc_p_clockticks > 1.000228813 789,833,783 unc_p_freq_max_os_cycles # 98.7 > 2.000654229 800,308,990 unc_p_clockticks > 2.000654229 396,214,238 unc_p_freq_max_os_cycles # 49.5 > > $ perf stat -a -I 1000 -e '{unc_p_clockticks,unc_p_freq_max_os_cycles}' --metric-only > 1.000206740 48.0 > 2.000451543 48.1 The comment above suggest I'll see 'original event as description' in this example?? However, could you just make those metric names working in here? Displaying original event for metric value is misleading. jirka