From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754795AbdJIOvd (ORCPT ); Mon, 9 Oct 2017 10:51:33 -0400 Received: from mail.kernel.org ([198.145.29.99]:37678 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752206AbdJIOvc (ORCPT ); Mon, 9 Oct 2017 10:51:32 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EAE18218DB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=acme@kernel.org Date: Mon, 9 Oct 2017 11:51:28 -0300 From: Arnaldo Carvalho de Melo To: Jiri Olsa Cc: Andi Kleen , Jiri Olsa , Wang Nan , linux-kernel@vger.kernel.org, Andi Kleen , He Kuang , Alexei Starovoitov Subject: Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case Message-ID: <20171009145128.GF28623@kernel.org> References: <20170912195643.2611-1-andi@firstfloor.org> <20170912195643.2611-2-andi@firstfloor.org> <20171003160605.GC25388@kernel.org> <20171004103052.GC23759@krava> <20171004162711.GF2482@two.firstfloor.org> <20171009134151.GA15127@krava> <20171009140728.GG2482@two.firstfloor.org> <20171009141258.GE28623@kernel.org> <20171009143953.GA1561@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171009143953.GA1561@krava> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.9.0 (2017-09-02) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Mon, Oct 09, 2017 at 04:39:53PM +0200, Jiri Olsa escreveu: > On Mon, Oct 09, 2017 at 11:12:58AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Mon, Oct 09, 2017 at 07:07:29AM -0700, Andi Kleen escreveu: > > > On Mon, Oct 09, 2017 at 03:41:51PM +0200, Jiri Olsa wrote: > > > > On Wed, Oct 04, 2017 at 09:27:11AM -0700, Andi Kleen wrote: > > > > > I tried similar patches, but I always ran into more complex > > > > > situations where it still matched incorrectly. > > > > > > > > > > e.g. try it with cpu/uops_executed.core,... vs uops_executed.core > > > > > > > > hm, both works for me with the change: > > > > > > > > perf stat -e cpu/uops_executed.core/ ls > > > > perf stat -e uops_executed.core ls > > > > > > Ok. If it works it's fine for me. > > well it works, but it means that bpf file cannot contains any directory > part.. which im not sure is ok with bpf folks ;-) anyone? That is a big limitation :-\ - Arnaldo