diff options
| author | Robin Murphy <robin.murphy@arm.com> | 2026-07-16 15:56:35 +0100 |
|---|---|---|
| committer | Will Deacon <will@kernel.org> | 2026-08-02 11:15:37 +0000 |
| commit | 745a724f9c81abd3c37c2d07daa855bd87e88120 (patch) | |
| tree | 494ca236eac6f0f73dc85bedf4c3bb8b4fc56868 /tools/perf/scripts/python/flamegraph.py | |
| parent | 04aa909b38bfe9a7e9b052f2c66b98d33f6f8a64 (diff) | |
perf/arm_cspmu: Improve APMT-based PMU naming
On ACPI systems, it has not actually been possible for userspace to
reliably tell which PMU corresponds to which APMT entry for types
other than "ACPI device" - the evidence trail only leads from the
arbitrarily-numbered PMU device to its arbitrarily-numbered parent
platform device that has no distinguishing features either.
While we've now improved the platform device creation to associate the
actual APMT unique ID, we may as well also tweak the PMU devices to
substitute the arbitrary number with a different arbitrary number that
might be more directly meaningful based on the APMT definitions.
We don't have an equivalent for Devicetree, but in that case the
platform devices are at least identifiable via their sysfs-visible
of_node.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Reviewed-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
[will: Remove unneeded semicolon reported by coccinelle]
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions
