[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5add76dc-ea92-9778-a65b-792f3ff17040@huawei.com>
Date: Fri, 28 Jun 2019 18:05:43 +0100
From: John Garry <john.garry@...wei.com>
To: Andi Kleen <ak@...ux.intel.com>
CC: <peterz@...radead.org>, <mingo@...hat.com>, <acme@...nel.org>,
<alexander.shishkin@...ux.intel.com>, <jolsa@...hat.com>,
<namhyung@...nel.org>, <tmricht@...ux.ibm.com>,
<brueckner@...ux.ibm.com>, <kan.liang@...ux.intel.com>,
<ben@...adent.org.uk>, <mathieu.poirier@...aro.org>,
<mark.rutland@....com>, <will.deacon@....com>,
<linux-kernel@...r.kernel.org>, <linuxarm@...wei.com>,
<linux-arm-kernel@...ts.infradead.org>,
<zhangshaokun@...ilicon.com>
Subject: Re: [PATCH v3 1/4] perf pmu: Support more complex PMU event aliasing
On 28/06/2019 16:33, Andi Kleen wrote:
>> + /*
>> + * Match more complex aliases where the alias name is a comma-delimited
>> + * list of tokens, orderly contained in the matching PMU name.
>> + *
>> + * Example: For alias "socket,pmuname" and PMU "socketX_pmunameY", we
>> + * match "socket" in "socketX_pmunameY" and then "pmuname" in
>> + * "pmunameY".
>
> This needs to be documented in some manpage.
Hi Andi,
As I see, today the man page does not mention the matching from the
alias events declared in the jsons.
The perf list command shows these aliases, so I am not sure how useful
that info is adding to the man page.
What the man page does mention is the glob matching on the PMU device
name - like how "imc" can match PMU device "uncore_imc_0", but I'm not
changing around this.
Thanks,
John
>
> -Andi
>
>
> .
>
Powered by blists - more mailing lists