linux/Documentation/ABI/testing/sysfs-bus-event_source-devices
Ian Rogers 518413d89c perf Documentation: Describe the PMU naming convention
It is an existing convention to use suffixes with PMU names. Try to
capture that convention so that future PMU devices may adhere to it.

The name of the file and date within the file try to follow existing
conventions, particularly sysfs-bus-event_source-devices-events.

Reviewed-by: James Clark <james.clark@arm.com>
Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Reviewed-by: Leo Yan <leo.yan@arm.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Ian Rogers <irogers@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Bharat Bhushan <bbhushan2@marvell.com>
Cc: Bhaskara Budiredla <bbudiredla@marvell.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: Robin Murphy <robin.murphy@arm.com>
Cc: Stephane Eranian <eranian@google.com>
Cc: Thomas Richter <tmricht@linux.ibm.com>
Cc: Tuan Phan <tuanphan@os.amperecomputing.com>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20240606044959.335715-1-irogers@google.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2024-12-23 13:53:08 -03:00

24 lines
1 KiB
Text

What: /sys/bus/event_source/devices/<pmu>
Date: 2014/02/24
Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Description: Performance Monitoring Unit (<pmu>)
Each <pmu> directory, for a PMU device, is a name
optionally followed by an underscore and then either a
decimal or hexadecimal number. For example, cpu is a
PMU name without a suffix as is intel_bts,
uncore_imc_0 is a PMU name with a 0 numeric suffix,
ddr_pmu_87e1b0000000 is a PMU name with a hex
suffix. The hex suffix must be more than two
characters long to avoid ambiguity with PMUs like the
S390 cpum_cf.
Tools can treat PMUs with the same name that differ by
suffix as instances of the same PMU for the sake of,
for example, opening an event. For example, the PMUs
uncore_imc_free_running_0 and
uncore_imc_free_running_1 have an event data_read;
opening the data_read event on a PMU specified as
uncore_imc_free_running should be treated as opening
the data_read event on PMU uncore_imc_free_running_0
and PMU uncore_imc_free_running_1.