From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754211AbdBITBN (ORCPT ); Thu, 9 Feb 2017 14:01:13 -0500 Received: from one.firstfloor.org ([193.170.194.197]:46135 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753304AbdBITAX (ORCPT ); Thu, 9 Feb 2017 14:00:23 -0500 Date: Thu, 9 Feb 2017 10:59:43 -0800 From: Andi Kleen To: Jiri Olsa Cc: Andi Kleen , Andi Kleen , acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 10/10] perf, tools, stat: Output JSON MetricExpr metric Message-ID: <20170209185942.GS26852@two.firstfloor.org> References: <20170128020345.19007-1-andi@firstfloor.org> <20170128020345.19007-11-andi@firstfloor.org> <20170208113134.GE10639@krava> <20170208215103.GP26852@two.firstfloor.org> <20170209113937.GA7455@krava> <20170209170035.GA15301@tassilo.jf.intel.com> <20170209183755.GA17928@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170209183755.GA17928@krava> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 09, 2017 at 07:37:55PM +0100, Jiri Olsa wrote: > > The last time I proposed separate files Ingo vetoed it. > > He wanted everything built in. > > sure, he veto it for event files.. expressions could be built > in same way as we have events now That's exactly what I implemented. The expression is part of the JSON file, which seems like the logical place. You just want it in a separate file in the source? > > > > from which point we could point and configure events we need > > > > If you want full flexibility you can use your perf stat report > > approach, or what most people do is to just run a script/spreadsheet > > over the the -x; output. This all continues to work. > > > > This is just a minimum approach to provide some convenience > > integrated with the event list to provide something similar > > as the built in expressions in stat-shadow. > > > > It's not trying to build the great perf scripting language. > > yea I understand that but can't ack that based on the points > I descibed in my other email So what are the crucial points that prevent you? - You want better column descriptions? I suppose could add another field for this. - You want multiple expressions per event (even though they are not needed today)? It could be implemented, but seems like unnecessary complexity and overengineering to me at this point. If nobody ever uses it would it be time spent well? If someone really uses it they could add the support at that time. - You want automatic group creation? It has nasty corner cases. It would be possible to build something that works for simple cases. Anything I missed? -Andi