From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934965AbaGPSWt (ORCPT ); Wed, 16 Jul 2014 14:22:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24981 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934741AbaGPSWp (ORCPT ); Wed, 16 Jul 2014 14:22:45 -0400 Date: Wed, 16 Jul 2014 20:22:14 +0200 From: Jiri Olsa To: Adrian Hunter Cc: Arnaldo Carvalho de Melo , Peter Zijlstra , linux-kernel@vger.kernel.org, David Ahern , Frederic Weisbecker , Namhyung Kim , Paul Mackerras , Stephane Eranian Subject: Re: [PATCH 20/41] perf tools: Let a user specify a PMU event without any config terms Message-ID: <20140716182214.GB32716@krava.redhat.com> References: <1405332185-4050-1-git-send-email-adrian.hunter@intel.com> <1405332185-4050-21-git-send-email-adrian.hunter@intel.com> <20140716142510.GE9441@krava.redhat.com> <53C6948C.2080103@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53C6948C.2080103@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 16, 2014 at 06:04:44PM +0300, Adrian Hunter wrote: > On 16/07/2014 5:25 p.m., Jiri Olsa wrote: > >On Mon, Jul 14, 2014 at 01:02:44PM +0300, Adrian Hunter wrote: > >>This enables a PMU event to be specified in the form: > >> > >> pmu// > >> > >>which is effectively the same as: > >> > >> pmu/config=0/ > >> > >>This patch is a precursor to defining > >>default config for a PMU. > > > >I understand the need for default config, but could you please elaborate > >why do we want to parse 'pmu//' as an event string string? > > Currently the parser requires the slashes to identify a PMU event > as opposed to a hardware or other kind of event. right, so why do we want to parse 'pmu//' as an event string? ;-) jirka