From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932225AbcJDIUD (ORCPT ); Tue, 4 Oct 2016 04:20:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51450 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752043AbcJDIUB (ORCPT ); Tue, 4 Oct 2016 04:20:01 -0400 Date: Tue, 4 Oct 2016 10:19:58 +0200 From: Jiri Olsa To: Arnaldo Carvalho de Melo Cc: Arnaldo Carvalho de Melo , Sukadev Bhattiprolu , peterz@infradead.org, maddy@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Jiri Olsa , Andi Kleen Subject: Re: [PATCH v21 16/19] perf, tools: Make alias matching case-insensitive Message-ID: <20161004081958.GB29784@krava> References: <1473978296-20712-1-git-send-email-sukadev@linux.vnet.ibm.com> <1473978296-20712-17-git-send-email-sukadev@linux.vnet.ibm.com> <20161004004706.GF7143@kernel.org> <20161004005448.GG7143@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161004005448.GG7143@kernel.org> User-Agent: Mutt/1.7.0 (2016-08-17) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Tue, 04 Oct 2016 08:20:01 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 03, 2016 at 09:54:48PM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, Oct 03, 2016 at 09:47:06PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Thu, Sep 15, 2016 at 03:24:53PM -0700, Sukadev Bhattiprolu escreveu: > > > From: Andi Kleen > > > > > > Make alias matching the events parser case-insensitive. This is useful > > > with the JSON events. perf uses lower case events, but the CPU manuals > > > generally use upper case event names. The JSON files use lower > > > case by default too. But if we search case insensitively then > > > users can cut-n-paste the upper case event names. > > > > > > So the following works: > > > > > > % perf stat -e BR_INST_EXEC.TAKEN_INDIRECT_NEAR_CALL true > > > > > > Performance counter stats for 'true': > > > > > > 305 BR_INST_EXEC.TAKEN_INDIRECT_NEAR_CALL > > > > > > 0.000492799 seconds time elapsed > > > > So now trying to figure this out: > > Ok, so this is just another case of bad patch ordering: this uses 'perf > stat' as the example, but it doesn't work at this point, one needs to go > to the last patch, apply it and then test it again, when it will work. > So just moved the last patch to before this one, sigh. ok, you found it.. sry ;-) jirka