From: John Garry <john.garry@huawei.com>
To: <Frank.li@nxp.com>, <will@kernel.org>, <mark.rutland@arm.com>,
<robh+dt@kernel.org>, <zhangshaokun@hisilicon.com>,
<qiangqing.zhang@nxp.com>
Cc: <linuxarm@huawei.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <acme@kernel.org>,
<jolsa@redhat.com>, <irogers@google.com>
Subject: Re: [PATCH v2 0/4] perf drivers: Add sysfs identifier file
Date: Fri, 6 Nov 2020 13:36:56 +0000 [thread overview]
Message-ID: <6b6b96d0-19c7-8be7-5742-ed01b5b891cc@huawei.com> (raw)
In-Reply-To: <1602149181-237415-1-git-send-email-john.garry@huawei.com>
On 08/10/2020 10:26, John Garry wrote:
Hi Will, Mark,
Can you have a look at this series please?
You were cc'ed on the v5 rebase of the userspace part which I sent out a
little while ago.
Cheers,
John
> To allow perf tool to identify a specific implementation of a PMU for
> event alias matching and metric support, expose a per-PMU identifier file.
>
> There is no standard format for the identifier string. It just should be
> unique per HW implementation.
>
> Typical methods to retrieve the information for the identifier string
> can include:
> - Hardcoding in the driver, matched via DT bindings compat string,
> ACPI HID, or similar
> - Directly from DT bindings property
> - Read from some HW identification register
>
> In this series, for the SMMUv3 PMU and HiSi uncore drivers, a HW ID
> register is read for the identifier. For the imx8 ddr driver, the
> identifier is hardcoded, matched via DT compat string.
>
> Joakim Zhang (2):
> bindings/perf/imx-ddr: update compatible string
> perf/imx_ddr: Add system PMU identifier for userspace
>
> John Garry (2):
> drivers/perf: hisi: Add identifier sysfs file
> perf/smmuv3: Support sysfs identifier file
>
> .../devicetree/bindings/perf/fsl-imx-ddr.txt | 3 ++
> drivers/perf/arm_smmuv3_pmu.c | 39 ++++++++++++++++
> drivers/perf/fsl_imx8_ddr_perf.c | 45 +++++++++++++++++--
> drivers/perf/hisilicon/hisi_uncore_ddrc_pmu.c | 16 +++++++
> drivers/perf/hisilicon/hisi_uncore_hha_pmu.c | 16 +++++++
> drivers/perf/hisilicon/hisi_uncore_l3c_pmu.c | 16 +++++++
> drivers/perf/hisilicon/hisi_uncore_pmu.c | 10 +++++
> drivers/perf/hisilicon/hisi_uncore_pmu.h | 7 +++
> 8 files changed, 149 insertions(+), 3 deletions(-)
>
next prev parent reply other threads:[~2020-11-06 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 9:26 [PATCH v2 0/4] perf drivers: Add sysfs identifier file John Garry
2020-10-08 9:26 ` [PATCH v2 1/4] drivers/perf: hisi: Add identifier sysfs file John Garry
2020-10-08 9:26 ` [PATCH v2 2/4] bindings/perf/imx-ddr: update compatible string John Garry
2020-10-12 9:58 ` Joakim Zhang
2020-10-08 9:26 ` [PATCH v2 3/4] perf/imx_ddr: Add system PMU identifier for userspace John Garry
2020-10-08 9:26 ` [PATCH v2 4/4] perf/smmuv3: Support sysfs identifier file John Garry
2020-11-06 13:36 ` John Garry [this message]
2020-11-25 15:44 ` [PATCH v2 0/4] perf drivers: Add " Will Deacon
2020-11-25 16:00 ` John Garry
2020-11-26 1:35 ` Joakim Zhang
2020-11-26 11:35 ` John Garry
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=6b6b96d0-19c7-8be7-5742-ed01b5b891cc@huawei.com \
--to=john.garry@huawei.com \
--cc=Frank.li@nxp.com \
--cc=acme@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@kernel.org \
--cc=will@kernel.org \
--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).