[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <160631703729.2332128.13220150013299384201.b4-ty@kernel.org>
Date: Wed, 25 Nov 2020 15:44:06 +0000
From: Will Deacon <will@...nel.org>
To: qiangqing.zhang@....com, zhangshaokun@...ilicon.com,
mark.rutland@....com, Frank.li@....com,
John Garry <john.garry@...wei.com>, robh+dt@...nel.org
Cc: catalin.marinas@....com, kernel-team@...roid.com,
Will Deacon <will@...nel.org>, acme@...nel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
irogers@...gle.com, jolsa@...hat.com, devicetree@...r.kernel.org,
linuxarm@...wei.com
Subject: Re: [PATCH v2 0/4] perf drivers: Add sysfs identifier file
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
Powered by blists - more mailing lists