From: Will Deacon <will@kernel.org>
To: qiangqing.zhang@nxp.com, zhangshaokun@hisilicon.com,
mark.rutland@arm.com, Frank.li@nxp.com,
John Garry <john.garry@huawei.com>,
robh+dt@kernel.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
acme@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, irogers@google.com,
jolsa@redhat.com, devicetree@vger.kernel.org,
linuxarm@huawei.com
Subject: Re: [PATCH v2 0/4] perf drivers: Add sysfs identifier file
Date: Wed, 25 Nov 2020 15:44:06 +0000 [thread overview]
Message-ID: <160631703729.2332128.13220150013299384201.b4-ty@kernel.org> (raw)
In-Reply-To: <1602149181-237415-1-git-send-email-john.garry@huawei.com>
On Thu, 8 Oct 2020 17:26:17 +0800, John Garry wrote:
> 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
>
> [...]
Applied the hisi and smmu parts to will (for-next/perf), thanks!
[1/4] drivers/perf: hisi: Add identifier sysfs file
https://git.kernel.org/will/c/ac4511c9364c
[...]
[4/4] perf/smmuv3: Support sysfs identifier file
https://git.kernel.org/will/c/2c255223362e
I've completely lost track of the imx ddr PMU, so I dropped those parts
(patch 3/4 seemed to remove a compatible string from the driver?).
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: qiangqing.zhang@nxp.com, zhangshaokun@hisilicon.com,
mark.rutland@arm.com, Frank.li@nxp.com,
John Garry <john.garry@huawei.com>,
robh+dt@kernel.org
Cc: irogers@google.com, Will Deacon <will@kernel.org>,
devicetree@vger.kernel.org, catalin.marinas@arm.com,
jolsa@redhat.com, linux-kernel@vger.kernel.org, acme@kernel.org,
linuxarm@huawei.com, kernel-team@android.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] perf drivers: Add sysfs identifier file
Date: Wed, 25 Nov 2020 15:44:06 +0000 [thread overview]
Message-ID: <160631703729.2332128.13220150013299384201.b4-ty@kernel.org> (raw)
In-Reply-To: <1602149181-237415-1-git-send-email-john.garry@huawei.com>
On Thu, 8 Oct 2020 17:26:17 +0800, John Garry wrote:
> 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
>
> [...]
Applied the hisi and smmu parts to will (for-next/perf), thanks!
[1/4] drivers/perf: hisi: Add identifier sysfs file
https://git.kernel.org/will/c/ac4511c9364c
[...]
[4/4] perf/smmuv3: Support sysfs identifier file
https://git.kernel.org/will/c/2c255223362e
I've completely lost track of the imx ddr PMU, so I dropped those parts
(patch 3/4 seemed to remove a compatible string from the driver?).
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
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:[~2020-11-25 15:44 UTC|newest]
Thread overview: 22+ 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 ` 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 ` John Garry
2020-10-08 9:26 ` [PATCH v2 2/4] bindings/perf/imx-ddr: update compatible string John Garry
2020-10-08 9:26 ` John Garry
2020-10-12 9:58 ` Joakim Zhang
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 ` John Garry
2020-10-08 9:26 ` [PATCH v2 4/4] perf/smmuv3: Support sysfs identifier file John Garry
2020-10-08 9:26 ` John Garry
2020-11-06 13:36 ` [PATCH v2 0/4] perf drivers: Add " John Garry
2020-11-06 13:36 ` John Garry
2020-11-25 15:44 ` Will Deacon [this message]
2020-11-25 15:44 ` Will Deacon
2020-11-25 16:00 ` John Garry
2020-11-25 16:00 ` John Garry
2020-11-26 1:35 ` Joakim Zhang
2020-11-26 1:35 ` Joakim Zhang
2020-11-26 11:35 ` John Garry
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=160631703729.2332128.13220150013299384201.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Frank.li@nxp.com \
--cc=acme@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=kernel-team@android.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.