From: John Garry <john.garry@huawei.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: mark.rutland@arm.com, brueckner@linux.ibm.com,
mathieu.poirier@linaro.org, peterz@infradead.org,
ben@decadent.org.uk, tmricht@linux.ibm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, acme@kernel.org,
linuxarm@huawei.com, zhangshaokun@hisilicon.com,
alexander.shishkin@linux.intel.com, mingo@redhat.com,
namhyung@kernel.org, jolsa@redhat.com,
linux-arm-kernel@lists.infradead.org, kan.liang@linux.intel.com
Subject: Re: [PATCH v3 1/4] perf pmu: Support more complex PMU event aliasing
Date: Fri, 28 Jun 2019 18:05:43 +0100 [thread overview]
Message-ID: <5add76dc-ea92-9778-a65b-792f3ff17040@huawei.com> (raw)
In-Reply-To: <20190628153344.GZ31027@tassilo.jf.intel.com>
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
>
>
> .
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-28 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 14:35 [PATCH v3 0/4] Perf uncore PMU event alias support for Hisi hip08 ARM64 platform John Garry
2019-06-28 14:35 ` [PATCH v3 1/4] perf pmu: Support more complex PMU event aliasing John Garry
2019-06-28 15:33 ` Andi Kleen
2019-06-28 17:05 ` John Garry [this message]
2019-07-02 19:07 ` Arnaldo Carvalho de Melo
2019-07-11 2:23 ` John Garry
2019-06-28 14:35 ` [PATCH v3 2/4] perf jevents: Add support for Hisi hip08 DDRC PMU aliasing John Garry
2019-06-28 14:35 ` [PATCH v3 3/4] perf jevents: Add support for Hisi hip08 HHA " John Garry
2019-06-28 14:35 ` [PATCH v3 4/4] perf jevents: Add support for Hisi hip08 L3C " John Garry
2019-06-28 14:54 ` [PATCH v3 0/4] Perf uncore PMU event alias support for Hisi hip08 ARM64 platform Jiri Olsa
2019-07-02 15:53 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5add76dc-ea92-9778-a65b-792f3ff17040@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben@decadent.org.uk \
--cc=brueckner@linux.ibm.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.com \
--cc=will.deacon@arm.com \
--cc=zhangshaokun@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).