[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150106094220.GB19868@krava.brq.redhat.com>
Date: Tue, 6 Jan 2015 10:42:20 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Michael Ellerman <mpe@...erman.id.au>,
Paul Mackerras <paulus@...ba.org>, dev@...yps.com,
peterz@...radead.org, hbabu@...ibm.com,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH v6 1/4] tools/perf: support parsing parameterized events
On Tue, Dec 23, 2014 at 11:58:50AM -0800, Sukadev Bhattiprolu wrote:
> From a24b480ff54381a7e092597864cf615162afdd60 Mon Sep 17 00:00:00 2001
> From: Cody P Schafer <cody@...ux.vnet.ibm.com>
> Date: Wed, 24 Sep 2014 12:27:15 -0700
> Subject: [PATCH 1/4] tools/perf: support parsing parameterized events
>
> Enable event specification like:
>
> pmu/event_name,param1=0x1,param2=0x4/
>
> Assuming that
>
> /sys/bus/event_source/devices/pmu/events/event_name
>
> Contains something like
>
> param2=?,bar=1,param1=?
>
> Changelog[v6]:
> [Jiri Olsa] Add a check to make sure that sysfs entries with
> parameters exactly match '=?'.
>
> Changelog[v4]:
> [Jiri Olsa] Merge to recent perf-core and fix a small conflict.
>
> Changelog[v3]:
> [Jiri Olsa] If the sysfs event file specifies 'param=val', make the
> usage 'hv_24x7/event,param=123/' rather than 'hv_24x7/event,val=123/'.
Acked-by: Jiri Olsa <jolsa@...nel.org>
I'm ok with whole patchset, with some nits for patch 2
that I've already sent out..
Would you mind sending v7 so we avoid confusion for Arnaldo
what to pick up?
thanks,
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists