perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo
v4 cover perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo
This is a completely new approach from V3 [1], although the metrics and event descriptions are autogenerated, the topdown metrics have been manually edited to use #no_stall_errata. This removes the need to duplicate the whole set of JSONs when only the topdown metrics are different between N2 and V2.
The CPU ID comparison function still needs to change so that the new literal can compare on versions, but now no change is needed to mapfile or the PMU event generation code because we still only support one set of JSONs per CPU.
[1]: https://lore.kernel.org/lkml/[email protected]/
------
Changes since v3:
* Instead of duplicating all the metrics, add a new expression literal that can be used to share the same metrics between N2 and V2
* Move tests to arch/arm64/tests
* Remove changes from jevents.py and mapfile.csv
Changes since v2:
* version -> variant in second commit message
* Add a bit more detail about version matching in the second commit message
* Update the comments in pmu-events/arch/arm64/mapfile.csv to say that variant and revision fields are now used
* Increase the CC list
Changes since v1:
* Split last change into two so it doesn't hit the mailing list size limit
James Clark (6):
perf: cs-etm: Don't duplicate FIELD_GET()
perf arm64: Allow version comparisons of CPU IDs
perf test: Add a test for the new Arm CPU ID comparison behavior perf vendor events arm64: Update scale units and descriptions of
common topdown metrics
perf vendor events arm64: Update stall_slot workaround for N2 r0p3 perf vendor events arm64: Update N2 and V2 metrics and events using
Arm telemetry repo
tools/perf/arch/arm64/include/arch-tests.h | 3 + tools/perf/arch/arm64/tests/Build | 1 + tools/perf/arch/arm64/tests/arch-tests.c | 4 + tools/perf/arch/arm64/tests/cpuid-match.c | 38 ++ tools/perf/arch/arm64/util/header.c | 64 ++- tools/perf/arch/arm64/util/pmu.c | 21 + .../arch/arm64/arm/neoverse-n2-v2/branch.json | 8 - .../arch/arm64/arm/neoverse-n2-v2/bus.json | 18 +- .../arch/arm64/arm/neoverse-n2-v2/cache.json | 155 -------- .../arm64/arm/neoverse-n2-v2/exception.json | 45 ++- .../arm/neoverse-n2-v2/fp_operation.json | 22 ++ .../arm64/arm/neoverse-n2-v2/general.json | 10 + .../arm64/arm/neoverse-n2-v2/instruction.json | 143 ------- .../arm64/arm/neoverse-n2-v2/l1d_cache.json | 54 +++ .../arm64/arm/neoverse-n2-v2/l1i_cache.json | 14 + .../arm64/arm/neoverse-n2-v2/l2_cache.json | 50 +++ .../arm64/arm/neoverse-n2-v2/l3_cache.json | 22 ++ .../arm64/arm/neoverse-n2-v2/ll_cache.json | 10 + .../arch/arm64/arm/neoverse-n2-v2/memory.json | 39 +- .../arm64/arm/neoverse-n2-v2/metrics.json | 365 ++++++++++-------- .../arm64/arm/neoverse-n2-v2/pipeline.json | 23 -- .../arm64/arm/neoverse-n2-v2/retired.json | 30 ++ .../arch/arm64/arm/neoverse-n2-v2/spe.json | 12 +- .../arm/neoverse-n2-v2/spec_operation.json | 110 ++++++ .../arch/arm64/arm/neoverse-n2-v2/stall.json | 30 ++ .../arch/arm64/arm/neoverse-n2-v2/sve.json | 50 +++ .../arch/arm64/arm/neoverse-n2-v2/tlb.json | 66 ++++ .../arch/arm64/arm/neoverse-n2-v2/trace.json | 27 +- tools/perf/pmu-events/arch/arm64/sbsa.json | 24 +- tools/perf/util/cs-etm.c | 14 +- tools/perf/util/expr.c | 4 + tools/perf/util/pmu.c | 6 + tools/perf/util/pmu.h | 1 + 33 files changed, 894 insertions(+), 589 deletions(-) create mode 100644 tools/perf/arch/arm64/tests/cpuid-match.c delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/branch.json delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/fp_operation.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/general.json delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/instruction.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l1d_cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l1i_cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l2_cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l3_cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ll_cache.json delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/pipeline.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/retired.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/spec_operation.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/stall.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/sve.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/tlb.json
Signature · 1 line
2.34.1
PATCH v4 1/6 perf: cs-etm: Don't duplicate FIELD_GET()
linux/bitfield.h can be included as long as linux/kernel.h is included first, so change the order of the includes and drop the duplicate macro.
--- tools/perf/util/cs-etm.c | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-)
tools/perf/util/cs-etm.c +2 -12
@@ -6,10 +6,11 @@* Author: Mathieu Poirier <[email protected]> */ +#include <linux/kernel.h> +#include <linux/bitfield.h> #include <linux/bitops.h> #include <linux/coresight-pmu.h> #include <linux/err.h> -#include <linux/kernel.h> #include <linux/log2.h> #include <linux/types.h> #include <linux/zalloc.h>
@@ -281,17 +282,6 @@ static int cs_etm__metadata_set_trace_id(u8 trace_chan_id, u64 *cpu_metadata)return 0 ; } -/* -* FIELD_GET (linux/bitfield.h) not available outside kernel code, -* and the header contains too many dependencies to just copy over, -* so roll our own based on the original -*/ -#define __bf_shf (x) (__builtin_ffsll(x) - 1) -#define FIELD_GET (_mask, _reg) \ - ({ \ - (typeof(_mask))(((_reg) & (_mask)) >> __bf_shf(_mask)); \ - }) -/* * Get a metadata for a specific cpu from an array. *
Signature · 1 line
2.34.1
Re: [PATCH v4 1/6] perf: cs-etm: Don't duplicate FIELD_GET()
Quoted 4 lines · James Clark
linux/bitfield.hcan be included as long aslinux/kernel.his included first, so change the order of the includes and drop the duplicate macro.Signed-off-by James Clark<[email protected]>
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH v4 2/6 perf arm64: Allow version comparisons of CPU IDs
In reply to James ClarkCurrently variant and revision fields are masked out of the MIDR so it's not possible to compare different versions of the same CPU. In a later commit a workaround will be removed just for N2 r0p3, so enable comparisons on version.
This has the side effect of changing the MIDR stored in the header of the perf.data file to no longer have masked version fields. It also affects the lookups in mapfile.csv, but as that currently only has zeroed version fields, it has no actual effect. The mapfile.csv documentation also states to zero the version fields, so unless this isn't done it will continue to have no effect.
--- tools/perf/arch/arm64/util/header.c | 64 ++++++++++++++++++++++------- 1 file changed, 50 insertions(+), 14 deletions(-)
tools/perf/arch/arm64/util/header.c +50 -14
@@ -1,3 +1,6 @@ +#include <linux/kernel.h> +#include <linux/bits.h> +#include <linux/bitfield.h> #include <stdio.h> #include <stdlib.h> #include <perf/cpumap.h>
@@ -10,14 +13,12 @@#define MIDR "/regs/identification/midr_el1"#define MIDR_SIZE 19 -#define MIDR_REVISION_MASK 0xf -#define MIDR_VARIANT_SHIFT 20 -#define MIDR_VARIANT_MASK (0xf << MIDR_VARIANT_SHIFT) +#define MIDR_REVISION_MASK GENMASK(3, 0) +#define MIDR_VARIANT_MASK GENMASK(23, 20)static int _get_cpuid (char *buf,size_t sz,struct perf_cpu_map *cpus) {const char *sysfs =sysfs__mountpoint (); -u64 midr =0 ;int cpu;if (!sysfs || sz <MIDR_SIZE )
@@ -44,21 +45,11 @@ static int _get_cpuid(char *buf, size_t sz, struct perf_cpu_map *cpus) }fclose (file); -/* Ignore/clear Variant[23:20] and -* Revision[3:0] of MIDR -*/ - midr =strtoul (buf,NULL ,16 ); - midr &= (~(MIDR_VARIANT_MASK |MIDR_REVISION_MASK )); -scnprintf (buf,MIDR_SIZE ,"0x%016lx" , midr);/* got midr break loop */ break ; }perf_cpu_map__put (cpus); - -if (!midr) -return EINVAL ; -return 0 ; }
@@ -99,3 +90,48 @@ char *get_cpuid_str(struct perf_pmu *pmu)return buf; } + +/* +* Return 0 if idstr is a higher or equal to version of the same part as +* mapcpuid. +* +* Therefore, if mapcpuid has 0 for revision and variant then any version of +* idstr will match as long as it's the same CPU type. +*/ +int strcmp_cpuid_str (const char *mapcpuid,const char *idstr) +{ +u64 map_id =strtoull (mapcpuid,NULL ,16 ); +char map_id_variant =FIELD_GET (MIDR_VARIANT_MASK , map_id); +char map_id_revision =FIELD_GET (MIDR_REVISION_MASK , map_id); +u64 id =strtoull (idstr,NULL ,16 ); +char id_variant =FIELD_GET (MIDR_VARIANT_MASK , id); +char id_revision =FIELD_GET (MIDR_REVISION_MASK , id); +u64 id_fields = ~(MIDR_VARIANT_MASK |MIDR_REVISION_MASK ); + +/* Compare without version first */ +if ((map_id & id_fields) != (id & id_fields)) +return 1 ; + +/* +* ID matches, now compare version. +* +* Arm revisions (like r0p0) are compared here like two digit semver +* values eg. 1.3 < 2.0 < 2.1 < 2.2. The events json file with the +* highest matching version is used. +* +* r = high value = 'Variant' field in MIDR +* p = low value = 'Revision' field in MIDR +* +*/ +if (id_variant > map_id_variant) +return 0 ; + +if (id_variant == map_id_variant && id_revision >= map_id_revision) +return 0 ; + +/* +* variant is less than mapfile variant or variants are the same but +* the revision doesn't match. Return no match. +*/ +return 1 ; +}
Signature · 1 line
2.34.1
PATCH v4 3/6 perf test: Add a test for the new Arm CPU ID comparison behavior
In reply to James ClarkNow that variant and revision fields are taken into account the behavior is slightly more complicated so add a test to ensure that this behaves as expected.
--- tools/perf/arch/arm64/include/arch-tests.h | 3 ++ tools/perf/arch/arm64/tests/Build | 1 + tools/perf/arch/arm64/tests/arch-tests.c | 4 +++ tools/perf/arch/arm64/tests/cpuid-match.c | 38 ++++++++++++++++++++++ 4 files changed, 46 insertions(+) create mode 100644 tools/perf/arch/arm64/tests/cpuid-match.c
tools/perf/arch/arm64/include/arch-tests.h +3 -0
@@ -2,6 +2,9 @@#ifndef ARCH_TESTS_H #define ARCH_TESTS_H +struct test_suite ; + +int test__cpuid_match (struct test_suite *test,int subtest);extern struct test_suite *arch_tests[];#endif
tools/perf/arch/arm64/tests/Build +1 -0
@@ -2,3 +2,4 @@ perf-y += regs_load.o perf-$(CONFIG_DWARF_UNWIND) += dwarf-unwind.o perf-y += arch-tests.o +perf-y += cpuid-match.o
tools/perf/arch/arm64/tests/arch-tests.c +4 -0
@@ -3,9 +3,13 @@#include "tests/tests.h" #include "arch-tests.h" + +DEFINE_SUITE ("arm64 CPUID matching" , cpuid_match); +struct test_suite *arch_tests[] = { #ifdef HAVE_DWARF_UNWIND_SUPPORT &suite__dwarf_unwind, #endif + &suite__cpuid_match,NULL , };
tools/perf/arch/arm64/tests/cpuid-match.c new file +38 -0
@@ -0,0 +1,38 @@ +// SPDX-License-Identifier: GPL-2.0 +#include <linux/compiler.h> + +#include "arch-tests.h" +#include "tests/tests.h" +#include "util/header.h" + +int test__cpuid_match (struct test_suite *test__maybe_unused , +int subtest__maybe_unused ) +{ +/* midr with no leading zeros matches */ +if (strcmp_cpuid_str ("0x410fd0c0" ,"0x00000000410fd0c0" )) +return -1 ; +/* Upper case matches */ +if (strcmp_cpuid_str ("0x410fd0c0" ,"0x00000000410FD0C0" )) +return -1 ; +/* r0p0 = r0p0 matches */ +if (strcmp_cpuid_str ("0x00000000410fd480" ,"0x00000000410fd480" )) +return -1 ; +/* r0p1 > r0p0 matches */ +if (strcmp_cpuid_str ("0x00000000410fd480" ,"0x00000000410fd481" )) +return -1 ; +/* r1p0 > r0p0 matches*/ +if (strcmp_cpuid_str ("0x00000000410fd480" ,"0x00000000411fd480" )) +return -1 ; +/* r0p0 < r0p1 doesn't match */ +if (!strcmp_cpuid_str ("0x00000000410fd481" ,"0x00000000410fd480" )) +return -1 ; +/* r0p0 < r1p0 doesn't match */ +if (!strcmp_cpuid_str ("0x00000000411fd480" ,"0x00000000410fd480" )) +return -1 ; +/* Different CPU doesn't match */ +if (!strcmp_cpuid_str ("0x00000000410fd4c0" ,"0x00000000430f0af0" )) +return -1 ; + +return 0 ; +} +
Signature · 1 line
2.34.1
PATCH v4 4/6 perf vendor events arm64: Update scale units and descriptions of common topdown metrics
In reply to James ClarkMetrics will be published here [1] going forwards, but they have slightly different scale units. To allow autogenerated metrics to be added more easily, update the scale units to match.
The more detailed descriptions have also been taken and added to the common file.
[1]: https://gitlab.arm.com/telemetry-solution/telemetry-solution/-/tree/main/data/pmu/cpu/
--- tools/perf/pmu-events/arch/arm64/sbsa.json | 24 +++++++++++----------- 1 file changed, 12 insertions(+), 12 deletions(-)
tools/perf/pmu-events/arch/arm64/sbsa.json +12 -12
@@ -1,34 +1,34 @@ [ { - "MetricExpr": "stall_slot_frontend / (#slots * cpu_cycles)", - "BriefDescription": "Frontend bound L1 topdown metric", + "MetricExpr": "100 * (stall_slot_frontend / (#slots * cpu_cycles))", + "BriefDescription": "This metric is the percentage of total slots that were stalled due to resource constraints in the frontend of the processor.", "DefaultMetricgroupName": "TopdownL1", "MetricGroup": "Default;TopdownL1", "MetricName": "frontend_bound", - "ScaleUnit": "100%" + "ScaleUnit": "1percent of slots" }, { - "MetricExpr": "(1 - op_retired / op_spec) * (1 - stall_slot / (#slots * cpu_cycles))", - "BriefDescription": "Bad speculation L1 topdown metric", + "MetricExpr": "100 * ((1 - op_retired / op_spec) * (1 - stall_slot / (#slots * cpu_cycles)))", + "BriefDescription": "This metric is the percentage of total slots that executed operations and didn't retire due to a pipeline flush.\nThis indicates cycles that were utilized but inefficiently.", "DefaultMetricgroupName": "TopdownL1", "MetricGroup": "Default;TopdownL1", "MetricName": "bad_speculation", - "ScaleUnit": "100%" + "ScaleUnit": "1percent of slots" }, { - "MetricExpr": "(op_retired / op_spec) * (1 - stall_slot / (#slots * cpu_cycles))", - "BriefDescription": "Retiring L1 topdown metric", + "MetricExpr": "100 * ((op_retired / op_spec) * (1 - stall_slot / (#slots * cpu_cycles)))", + "BriefDescription": "This metric is the percentage of total slots that retired operations, which indicates cycles that were utilized efficiently.", "DefaultMetricgroupName": "TopdownL1", "MetricGroup": "Default;TopdownL1", "MetricName": "retiring", - "ScaleUnit": "100%" + "ScaleUnit": "1percent of slots" }, { - "MetricExpr": "stall_slot_backend / (#slots * cpu_cycles)", - "BriefDescription": "Backend Bound L1 topdown metric", + "MetricExpr": "100 * (stall_slot_backend / (#slots * cpu_cycles))", + "BriefDescription": "This metric is the percentage of total slots that were stalled due to resource constraints in the backend of the processor.", "DefaultMetricgroupName": "TopdownL1", "MetricGroup": "Default;TopdownL1", "MetricName": "backend_bound", - "ScaleUnit": "100%" + "ScaleUnit": "1percent of slots" } ]
Signature · 1 line
2.34.1
Re: [PATCH v4 4/6] perf vendor events arm64: Update scale units and descriptions of common topdown metrics
Quoted 6 lines · James Clark
Metrics will be published here [1] going forwards, but they have slightly different scale units. To allow autogenerated metrics to be added more easily, update the scale units to match.
The more detailed descriptions have also been taken and added to the common file.
It's unfortunate that we can't have a concise description - like which we have now - and a full description.
Quoted 1 line
Anyway,
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v4 4/6] perf vendor events arm64: Update scale units and descriptions of common topdown metrics
Quoted 8 lines · John Garry
Quoted 6 lines · James Clark
Metrics will be published here [1] going forwards, but they have slightly different scale units. To allow autogenerated metrics to be added more easily, update the scale units to match.
The more detailed descriptions have also been taken and added to the common file.
Quoted 8 lines
It's unfortunate that we can't have a concise description - like which we have now - and a full description.
Quoted 1 line
Anyway,
Reviewed-by John Garry <[email protected]>
Yes unfortunately in the source data the metric short description ("title") pretty much just matches the metric name but without underscores. For that reason we chose not to use it for Perf's short description otherwise the list command showed a lot of duplication.
"frontend_bound": {
"title": "Frontend Bound",
"description": "This metric is the percentage of...
The PMU events on the other hand do have a short description in the title field rather than just repeating the name:
ITLB_WALK": {
"code": "0x0035",
"title": "Instruction TLB access with at least one translation table
walk",
"description": "Counts instruction memory translation table walks
caused by a miss in the L2...
I can raise this internally as it does seem to be a bit of an inconsistency.
James
PATCH v4 5/6 perf vendor events arm64: Update stall_slot workaround for N2 r0p3
In reply to James ClarkN2 r0p3 doesn't require the workaround [1], so gating on (#slots - 5) no longer works because all N2s have 5 slots. Add a new expression builtin that identifies the need for the workaround correctly.
--- tools/perf/arch/arm64/util/pmu.c | 21 +++++++++++++++++++ .../arm64/arm/neoverse-n2-v2/metrics.json | 8 +++---- tools/perf/util/expr.c | 4 ++++ tools/perf/util/pmu.c | 6 ++++++ tools/perf/util/pmu.h | 1 + 5 files changed, 36 insertions(+), 4 deletions(-)
tools/perf/arch/arm64/util/pmu.c +21 -0
@@ -2,6 +2,7 @@#include <internal/cpumap.h> #include "../../../util/cpumap.h" +#include "../../../util/header.h" #include "../../../util/pmu.h" #include "../../../util/pmus.h" #include <api/fs/fs.h>
@@ -62,3 +63,23 @@ double perf_pmu__cpu_slots_per_cycle(void)return slots ? (double )slots :NAN ; } + +double perf_pmu__no_stall_errata (void ) +{ +struct perf_pmu *pmu =pmu__find_core_pmu (); +char *cpuid =perf_pmu__getcpuid (pmu); +bool n2_r0p3_plus; +bool not_n2; + +if (!cpuid) +return NAN ; + +/* N2 r0p3+ doesn't need CPU_CYCLES to be subtracted from slots. */ + n2_r0p3_plus = !strcmp_cpuid_str ("0x00000000410fd493" , cpuid); + +/* Anything other than N2 doesn't need the workaround either */ + not_n2 =strcmp_cpuid_str ("0x00000000410fd490" , cpuid); + +free (cpuid); +return n2_r0p3_plus || not_n2; +}
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/metrics.json +4 -4
@@ -1,15 +1,15 @@ [ { "ArchStdEvent": "FRONTEND_BOUND", - "MetricExpr": "((stall_slot_frontend) if (#slots - 5) else (stall_slot_frontend - cpu_cycles)) / (#slots * cpu_cycles)" + "MetricExpr": "((stall_slot_frontend) if (#no_stall_errata) else (stall_slot_frontend - cpu_cycles)) / (#slots * cpu_cycles)" }, { "ArchStdEvent": "BAD_SPECULATION", - "MetricExpr": "(1 - op_retired / op_spec) * (1 - (stall_slot if (#slots - 5) else (stall_slot - cpu_cycles)) / (#slots * cpu_cycles))" + "MetricExpr": "(1 - op_retired / op_spec) * (1 - (stall_slot if (#no_stall_errata) else (stall_slot - cpu_cycles)) / (#slots * cpu_cycles))" }, { "ArchStdEvent": "RETIRING", - "MetricExpr": "(op_retired / op_spec) * (1 - (stall_slot if (#slots - 5) else (stall_slot - cpu_cycles)) / (#slots * cpu_cycles))" + "MetricExpr": "(op_retired / op_spec) * (1 - (stall_slot if (#no_stall_errata) else (stall_slot - cpu_cycles)) / (#slots * cpu_cycles))" }, { "ArchStdEvent": "BACKEND_BOUND"
@@ -201,7 +201,7 @@ "ScaleUnit": "100%" }, { - "MetricExpr": "OP_RETIRED / OP_SPEC * (1 - (STALL_SLOT if (#slots - 5) else (STALL_SLOT - CPU_CYCLES)) / (#slots * CPU_CYCLES))", + "MetricExpr": "OP_RETIRED / OP_SPEC * (1 - (STALL_SLOT if (#no_stall_errata) else (STALL_SLOT - CPU_CYCLES)) / (#slots * CPU_CYCLES))", "BriefDescription": "The truly effective ratio of micro-operations executed by the CPU, which means that misprediction and stall are not included", "MetricGroup": "PEutilization", "MetricName": "cpu_utilization",
tools/perf/util/expr.c +4 -0
@@ -465,6 +465,10 @@ double expr__get_literal(const char *literal, const struct expr_scanner_ctx *ctx result =perf_pmu__cpu_slots_per_cycle (); goto out; } +if (!strcmp ("#no_stall_errata" , literal)) { + result =perf_pmu__no_stall_errata (); + goto out; + }if (!strcmp ("#has_pmem" , literal)) { result =has_pmem (); goto out;
tools/perf/util/pmu.c +6 -0
@@ -1779,3 +1779,9 @@ void perf_pmu__delete(struct perf_pmu *pmu)zfree (&pmu->alias_name);free (pmu); } + +__weak double perf_pmu__no_stall_errata (void ) +{ +/* Only exists on Arm */ +return NAN ; +}
tools/perf/util/pmu.h +1 -0
@@ -288,5 +288,6 @@ int perf_pmu__pathname_fd(int dirfd, const char *pmu_name, const char *filename,struct perf_pmu *perf_pmu__lookup (struct list_head *pmus,int dirfd,const char *lookup_name);struct perf_pmu *perf_pmu__create_placeholder_core_pmu (struct list_head *core_pmus);void perf_pmu__delete (struct perf_pmu *pmu); +double perf_pmu__no_stall_errata (void );#endif /* __PMU_H */
Signature · 1 line
2.34.1
John Garry
reviewerRe: [PATCH v4 5/6] perf vendor events arm64: Update stall_slot workaround for N2 r0p3
On 07/08/2023 15:20, James Clark wrote:
Hi James,
Thanks for the effort in doing this.
Quoted 27 lines
N2 r0p3 doesn't require the workaround [1], so gating on (#slots - 5) no longer works because all N2s have 5 slots. Add a new expression builtin that identifies the need for the workaround correctly.
Signed-off-by James Clark <[email protected]>--- tools/perf/arch/arm64/util/pmu.c | 21 +++++++++++++++++++ .../arm64/arm/neoverse-n2-v2/metrics.json | 8 +++---- tools/perf/util/expr.c | 4 ++++ tools/perf/util/pmu.c | 6 ++++++ tools/perf/util/pmu.h | 1 + 5 files changed, 36 insertions(+), 4 deletions(-)tools/perf/arch/arm64/util/pmu.c +1
-0@@ -2,6 +2,7 @@#include <internal/cpumap.h> #include "../../../util/cpumap.h" +#include "../../../util/header.h" #include "../../../util/pmu.h" #include "../../../util/pmus.h" #include <api/fs/fs.h>
tools/perf/arch/arm64/util/pmu.c double perf_pmu__cpu_slots_per_cycle(void) · line 67
Quoted 5 lines
tools/perf/arch/arm64/util/pmu.c +2
-0@@ -62,3 +63,23 @@ double perf_pmu__cpu_slots_per_cycle(void)return slots ? (double )slots :NAN ; } + +double perf_pmu__no_stall_errata (void )
While I like the approach of encoding the per-CPU support in the metric expression, I find that literal "no stall errata" is vague and could apply to any "stall errata" for any SoC for any architecture.
If we were going to do it this way, then we would need a more specific name, like perf_pmu__no_stall_errata_arm64_errata123456(), but that should not be in the core perf code.
Could we instead add a function to check cpuid and have something like this in the JSON:
"MetricExpr": "(op_retired / op_spec) * (1 - (stall_slot if (cpuid_less_than(410fd493)) else (stall_slot - cpu_cycles)) / (#slots * cpu_cycles))"
I'm currently figuring out how cpuid_less_than() would be implemented (I'm no great python wrangler), but it would be along the lines of what Ian added for "has_event" in https://lore.kernel.org/linux-perf-users/[email protected]/
Thanks,
John
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v4 5/6] perf vendor events arm64: Update stall_slot workaround for N2 r0p3
Quoted 54 lines · John Garry
On 07/08/2023 15:20, James Clark wrote:
Hi James,
Thanks for the effort in doing this.
Quoted 28 lines
N2 r0p3 doesn't require the workaround [1], so gating on (#slots - 5) no longer works because all N2s have 5 slots. Add a new expression builtin that identifies the need for the workaround correctly.
Signed-off-by James Clark <[email protected]>---
tools/perf/arch/arm64/util/pmu.c | 21 +++++++++++++++++++ .../arm64/arm/neoverse-n2-v2/metrics.json | 8 +++---- tools/perf/util/expr.c | 4 ++++ tools/perf/util/pmu.c | 6 ++++++ tools/perf/util/pmu.h | 1 +5 files changed, 36 insertions(+), 4 deletions(-)tools/perf/arch/arm64/util/pmu.c +1
-0@@ -2,6 +2,7 @@ #include <internal/cpumap.h> #include "../../../util/cpumap.h" +#include "../../../util/header.h" #include "../../../util/pmu.h" #include "../../../util/pmus.h" #include <api/fs/fs.h>tools/perf/arch/arm64/util/pmu.c double perf_pmu__cpu_slots_per_cycle(void) · line 66
Quoted 4 lines
tools/perf/arch/arm64/util/pmu.c +2
-0@@ -62,3 +63,23 @@ double perf_pmu__cpu_slots_per_cycle(void) return slots ? (double)slots : NAN; } + +double perf_pmu__no_stall_errata (void )While I like the approach of encoding the per-CPU support in the metric expression, I find that literal "no stall errata" is vague and could apply to any "stall errata" for any SoC for any architecture.
If we were going to do it this way, then we would need a more specific name, like
perf_pmu__no_stall_errata_arm64_errata123456(), but that should not be in the core perf code.Could we instead add a function to check cpuid and have something like this in the JSON:
"MetricExpr": "(
op_retired/op_spec) * (1 - (stall_slotif (cpuid_less_than(410fd493)) else (stall_slot-cpu_cycles)) / (#slots *cpu_cycles))"
Quoted 7 lines
I'm currently figuring out how
cpuid_less_than()would be implemented (I'm no great python wrangler), but it would be along the lines of what Ian added for "has_event" in
https://lore.kernel.org/linux-perf-users/[email protected]/Thanks,
John
Yeah it looks like it could be done that way. Also, the way I added it, it doesn't have access to the PMU type, it just does a generic pmu__find_core_pmu() so won't work very well for heterogeneous systems.
If we're going to do a deeper modification of the expression parser like with has_event() it might be possible to pass in the actual CPU ID that the metric is running on which would be better.
I'll have a look.
James
John Garry
reviewerRe: [PATCH v4 5/6] perf vendor events arm64: Update stall_slot workaround for N2 r0p3
Quoted 9 lines · James Clark
Quoted 9 lines
"MetricExpr": "(
op_retired/op_spec) * (1 - (stall_slotif (cpuid_less_than(410fd493)) else (stall_slot-cpu_cycles)) / (#slots *cpu_cycles))"I'm currently figuring out how
cpuid_less_than()would be implemented (I'm no great python wrangler), but it would be along the lines of what Ian added for "has_event" inhttps://urldefense.com/v3/__https://lore.kernel.org/linux-perf-users/[email protected]/__;!!ACWV5N9M2RV99hQ!PlOppEWtIj9jDW2Zlon0zRZVpzPTzPvm5Ho5NnRIN0vD78iFcEzMEAtsrW_MrRPiW84XhWpbhc3seQcmLu-BfQ$
Quoted 5 lines
Quoted 2 lines
Thanks,
JohnYeah it looks like it could be done that way. Also, the way I added it, it doesn't have access to the PMU type, it just does a generic
pmu__find_core_pmu()so won't work very well for heterogeneous systems.
I haven't been keeping a close eye on the hybrid PMU support, but AFAIK metrics for hybrid arm64 system, i.e. bL, aren't supported - maybe that has changed. The gating for bL support was in pmu__find_core_pmu() returning NULL for a hybrid system.
Quoted 6 lines
If we're going to do a deeper modification of the expression parser like with
has_event()it might be possible to pass in the actual CPU ID that the metric is running on which would be better.I'll have a look.
Thanks. I was playing with this yesterday, but I was making slow progress. I was essentially following the has_event example, but the argument type causes an issue, in that has_event expected an event name, while we want to pass a hex string.
If you could check this then that would be great.
Thanks,
John
Re: [PATCH v4 5/6] perf vendor events arm64: Update stall_slot workaround for N2 r0p3
Quoted 11 lines · John Garry
Quoted 10 lines · James Clark
Quoted 10 lines
"MetricExpr": "(
op_retired/op_spec) * (1 - (stall_slotif (cpuid_less_than(410fd493)) else (stall_slot-cpu_cycles)) / (#slots *cpu_cycles))"I'm currently figuring out how
cpuid_less_than()would be implemented (I'm no great python wrangler), but it would be along the lines of what Ian added for "has_event" in
https://urldefense.com/v3/__https://lore.kernel.org/linux-perf-users/[email protected]/__;!!ACWV5N9M2RV99hQ!PlOppEWtIj9jDW2Zlon0zRZVpzPTzPvm5Ho5NnRIN0vD78iFcEzMEAtsrW_MrRPiW84XhWpbhc3seQcmLu-BfQ$
Thanks,
John
Quoted 9 lines
Quoted 3 lines
Yeah it looks like it could be done that way. Also, the way I added it, it doesn't have access to the PMU type, it just does a generic
pmu__find_core_pmu()so won't work very well for heterogeneous systems.I haven't been keeping a close eye on the hybrid PMU support, but AFAIK metrics for hybrid arm64 system, i.e. bL, aren't supported - maybe that has changed. The gating for bL support was in
pmu__find_core_pmu()returning NULL for a hybrid system.
Yes we're not currently publishing any metrics for hybrid systems, so in this case for N2 and V2 it's not needed. But it would be good to try to future proof it if possible. Although I don't know how the metrics currently react on hybrid systems, it's also something I have to take a look at.
Quoted 17 lines
Quoted 6 lines
If we're going to do a deeper modification of the expression parser like with
has_event()it might be possible to pass in the actual CPU ID that the metric is running on which would be better.I'll have a look.
Thanks. I was playing with this yesterday, but I was making slow progress. I was essentially following the
has_eventexample, but the argument type causes an issue, in thathas_eventexpected an event name, while we want to pass a hex string.If you could check this then that would be great.
Thanks,
John
PATCH v4 6/6 perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo
In reply to James ClarkApart from some slight naming and grouping differences, the new metrics are functionally the same as the existing ones. Any missing metrics were manually appended to the end of the auto generated file.
For the events, the new data includes descriptions that may have product specific details and new groupings that will be consistent with other products.
After generating the metrics from the telemetry repo [1], the following manual steps were performed:
* Change the topdown expressions to include #no_stall_errata and #slots so that the same data can be shared between N2 and V2. Apart from these modifications, the expressions now match more closely with the Arm telemetry data which will hopefully make future updates easier.
* Append some metrics from the old N2/V2 data that aren't present in the telemetry data. These will possibly be added to the telemetry-solution repo at a later time:
l3d_cache_mpki, l3d_cache_miss_rate, branch_pki, ipc_rate, spec_ipc, retired_rate, wasted_rate, branch_immed_spec_rate, branch_return_spec_rate, branch_indirect_spec_rate
--- .../arch/arm64/arm/neoverse-n2-v2/branch.json | 8 - .../arch/arm64/arm/neoverse-n2-v2/bus.json | 18 +- .../arch/arm64/arm/neoverse-n2-v2/cache.json | 155 -------- .../arm64/arm/neoverse-n2-v2/exception.json | 45 ++- .../arm/neoverse-n2-v2/fp_operation.json | 22 ++ .../arm64/arm/neoverse-n2-v2/general.json | 10 + .../arm64/arm/neoverse-n2-v2/instruction.json | 143 ------- .../arm64/arm/neoverse-n2-v2/l1d_cache.json | 54 +++ .../arm64/arm/neoverse-n2-v2/l1i_cache.json | 14 + .../arm64/arm/neoverse-n2-v2/l2_cache.json | 50 +++ .../arm64/arm/neoverse-n2-v2/l3_cache.json | 22 ++ .../arm64/arm/neoverse-n2-v2/ll_cache.json | 10 + .../arch/arm64/arm/neoverse-n2-v2/memory.json | 39 +- .../arm64/arm/neoverse-n2-v2/metrics.json | 365 ++++++++++-------- .../arm64/arm/neoverse-n2-v2/pipeline.json | 23 -- .../arm64/arm/neoverse-n2-v2/retired.json | 30 ++ .../arch/arm64/arm/neoverse-n2-v2/spe.json | 12 +- .../arm/neoverse-n2-v2/spec_operation.json | 110 ++++++ .../arch/arm64/arm/neoverse-n2-v2/stall.json | 30 ++ .../arch/arm64/arm/neoverse-n2-v2/sve.json | 50 +++ .../arch/arm64/arm/neoverse-n2-v2/tlb.json | 66 ++++ .../arch/arm64/arm/neoverse-n2-v2/trace.json | 27 +- 22 files changed, 752 insertions(+), 551 deletions(-) delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/branch.json delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/fp_operation.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/general.json delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/instruction.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l1d_cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l1i_cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l2_cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l3_cache.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ll_cache.json delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/pipeline.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/retired.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/spec_operation.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/stall.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/sve.json create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/tlb.json
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/branch.json deleted +0 -8
@@ -1,8 +0,0 @@ -[ - { - "ArchStdEvent": "BR_MIS_PRED" - }, - { - "ArchStdEvent": "BR_PRED" - } -]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/bus.json +8 -10
@@ -1,20 +1,18 @@ [ { - "ArchStdEvent": "CPU_CYCLES" + "ArchStdEvent": "BUS_ACCESS", + "PublicDescription": "Counts memory transactions issued by the CPU to the external bus, including snoop requests and snoop responses. Each beat of data is counted individually." }, { - "ArchStdEvent": "BUS_ACCESS" + "ArchStdEvent": "BUS_CYCLES", + "PublicDescription": "Counts bus cycles in the CPU. Bus cycles represent a clock cycle in which a transaction could be sent or received on the interface from the CPU to the external bus. Since that interface is driven at the same clock speed as the CPU, this event is a duplicate of CPU_CYCLES." }, { - "ArchStdEvent": "BUS_CYCLES" + "ArchStdEvent": "BUS_ACCESS_RD", + "PublicDescription": "Counts memory read transactions seen on the external bus. Each beat of data is counted individually." }, { - "ArchStdEvent": "BUS_ACCESS_RD" - }, - { - "ArchStdEvent": "BUS_ACCESS_WR" - }, - { - "ArchStdEvent": "CNT_CYCLES" + "ArchStdEvent": "BUS_ACCESS_WR", + "PublicDescription": "Counts memory write transactions seen on the external bus. Each beat of data is counted individually." } ]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/cache.json deleted +0 -155
155 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/exception.json +30 -15
77 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/fp_operation.json new file +22 -0
@@ -0,0 +1,22 @@ +[ + { + "ArchStdEvent": "FP_HP_SPEC", + "PublicDescription": "Counts speculatively executed half precision floating point operations." + }, + { + "ArchStdEvent": "FP_SP_SPEC", + "PublicDescription": "Counts speculatively executed single precision floating point operations." + }, + { + "ArchStdEvent": "FP_DP_SPEC", + "PublicDescription": "Counts speculatively executed double precision floating point operations." + }, + { + "ArchStdEvent": "FP_SCALE_OPS_SPEC", + "PublicDescription": "Counts speculatively executed scalable single precision floating point operations." + }, + { + "ArchStdEvent": "FP_FIXED_OPS_SPEC", + "PublicDescription": "Counts speculatively executed non-scalable single precision floating point operations." + } +]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/general.json new file +10 -0
@@ -0,0 +1,10 @@ +[ + { + "ArchStdEvent": "CPU_CYCLES", + "PublicDescription": "Counts CPU clock cycles (not timer cycles). The clock measured by this event is defined as the physical clock driving the CPU logic." + }, + { + "ArchStdEvent": "CNT_CYCLES", + "PublicDescription": "Counts constant frequency cycles" + } +]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/instruction.json deleted +0 -143
143 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l1d_cache.json new file +54 -0
54 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l1i_cache.json new file +14 -0
@@ -0,0 +1,14 @@ +[ + { + "ArchStdEvent": "L1I_CACHE_REFILL", + "PublicDescription": "Counts cache line refills in the level 1 instruction cache caused by a missed instruction fetch. Instruction fetches may include accessing multiple instructions, but the single cache line allocation is counted once." + }, + { + "ArchStdEvent": "L1I_CACHE", + "PublicDescription": "Counts instruction fetches which access the level 1 instruction cache. Instruction cache accesses caused by cache maintenance operations are not counted." + }, + { + "ArchStdEvent": "L1I_CACHE_LMISS", + "PublicDescription": "Counts cache line refills into the level 1 instruction cache, that incurred additional latency." + } +]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l2_cache.json new file +50 -0
50 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/l3_cache.json new file +22 -0
@@ -0,0 +1,22 @@ +[ + { + "ArchStdEvent": "L3D_CACHE_ALLOCATE", + "PublicDescription": "Counts level 3 cache line allocates that do not fetch data from outside the level 3 data or unified cache. For example, allocates due to streaming stores." + }, + { + "ArchStdEvent": "L3D_CACHE_REFILL", + "PublicDescription": "Counts level 3 accesses that receive data from outside the L3 cache." + }, + { + "ArchStdEvent": "L3D_CACHE", + "PublicDescription": "Counts level 3 cache accesses. level 3 cache is a unified cache for data and instruction accesses. Accesses are for misses in the lower level caches or translation resolutions due to accesses." + }, + { + "ArchStdEvent": "L3D_CACHE_RD", + "PublicDescription": "TBD" + }, + { + "ArchStdEvent": "L3D_CACHE_LMISS_RD", + "PublicDescription": "Counts any cache line refill into the level 3 cache from memory read operations that incurred additional latency." + } +]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ll_cache.json new file +10 -0
@@ -0,0 +1,10 @@ +[ + { + "ArchStdEvent": "LL_CACHE_RD", + "PublicDescription": "Counts read transactions that were returned from outside the core cluster. This event counts when the system register CPUECTLR.EXTLLC bit is set. This event counts read transactions returned from outside the core if those transactions are either hit in the system level cache or missed in the SLC and are returned from any other external sources." + }, + { + "ArchStdEvent": "LL_CACHE_MISS_RD", + "PublicDescription": "Counts read transactions that were returned from outside the core cluster but missed in the system level cache. This event counts when the system register CPUECTLR.EXTLLC bit is set. This event counts read transactions returned from outside the core if those transactions are missed in the System level Cache. The data source of the transaction is indicated by a field in the CHI transaction returning to the CPU. This event does not count reads caused by cache maintenance operations." + } +]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/memory.json +22 -17
@@ -1,41 +1,46 @@ [ { - "ArchStdEvent": "MEM_ACCESS" + "ArchStdEvent": "MEM_ACCESS", + "PublicDescription": "Counts memory accesses issued by the CPU load store unit, where those accesses are issued due to load or store operations. This event counts memory accesses no matter whether the data is received from any level of cache hierarchy or external memory. If memory accesses are broken up into smaller transactions than what were specified in the load or store instructions, then the event counts those smaller memory transactions." }, { - "ArchStdEvent": "REMOTE_ACCESS" + "ArchStdEvent": "MEMORY_ERROR", + "PublicDescription": "Counts any detected correctable or uncorrectable physical memory errors (ECC or parity) in protected CPUs RAMs. On the core, this event counts errors in the caches (including data and tag rams). Any detected memory error (from either a speculative and abandoned access, or an architecturally executed access) is counted. Note that errors are only detected when the actual protected memory is accessed by an operation." }, { - "ArchStdEvent": "MEM_ACCESS_RD" + "ArchStdEvent": "REMOTE_ACCESS", + "PublicDescription": "Counts accesses to another chip, which is implemented as a different CMN mesh in the system. If the CHI bus response back to the core indicates that the data source is from another chip (mesh), then the counter is updated. If no data is returned, even if the system snoops another chip/mesh, then the counter is not updated." }, { - "ArchStdEvent": "MEM_ACCESS_WR" + "ArchStdEvent": "MEM_ACCESS_RD", + "PublicDescription": "Counts memory accesses issued by the CPU due to load operations. The event counts any memory load access, no matter whether the data is received from any level of cache hierarchy or external memory. The event also counts atomic load operations. If memory accesses are broken up by the load/store unit into smaller transactions that are issued by the bus interface, then the event counts those smaller transactions." }, { - "ArchStdEvent": "UNALIGNED_LD_SPEC" + "ArchStdEvent": "MEM_ACCESS_WR", + "PublicDescription": "Counts memory accesses issued by the CPU due to store operations. The event counts any memory store access, no matter whether the data is located in any level of cache or external memory. The event also counts atomic load and store operations. If memory accesses are broken up by the load/store unit into smaller transactions that are issued by the bus interface, then the event counts those smaller transactions." }, { - "ArchStdEvent": "UNALIGNED_ST_SPEC" + "ArchStdEvent": "LDST_ALIGN_LAT", + "PublicDescription": "Counts the number of memory read and write accesses in a cycle that incurred additional latency, due to the alignment of the address and the size of data being accessed, which results in store crossing a single cache line." }, { - "ArchStdEvent": "UNALIGNED_LDST_SPEC" + "ArchStdEvent": "LD_ALIGN_LAT", + "PublicDescription": "Counts the number of memory read accesses in a cycle that incurred additional latency, due to the alignment of the address and size of data being accessed, which results in load crossing a single cache line." }, { - "ArchStdEvent": "LDST_ALIGN_LAT" + "ArchStdEvent": "ST_ALIGN_LAT", + "PublicDescription": "Counts the number of memory write access in a cycle that incurred additional latency, due to the alignment of the address and size of data being accessed incurred additional latency." }, { - "ArchStdEvent": "LD_ALIGN_LAT" + "ArchStdEvent": "MEM_ACCESS_CHECKED", + "PublicDescription": "Counts the number of memory read and write accesses in a cycle that are tag checked by the Memory Tagging Extension (MTE)." }, { - "ArchStdEvent": "ST_ALIGN_LAT" + "ArchStdEvent": "MEM_ACCESS_CHECKED_RD", + "PublicDescription": "Counts the number of memory read accesses in a cycle that are tag checked by the Memory Tagging Extension (MTE)." }, { - "ArchStdEvent": "MEM_ACCESS_CHECKED" - }, - { - "ArchStdEvent": "MEM_ACCESS_CHECKED_RD" - }, - { - "ArchStdEvent": "MEM_ACCESS_CHECKED_WR" + "ArchStdEvent": "MEM_ACCESS_CHECKED_WR", + "PublicDescription": "Counts the number of memory write accesses in a cycle that is tag checked by the Memory Tagging Extension (MTE)." } ]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/metrics.json +198 -167
470 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/pipeline.json deleted +0 -23
@@ -1,23 +0,0 @@ -[ - { - "ArchStdEvent": "STALL_FRONTEND" - }, - { - "ArchStdEvent": "STALL_BACKEND" - }, - { - "ArchStdEvent": "STALL" - }, - { - "ArchStdEvent": "STALL_SLOT_BACKEND" - }, - { - "ArchStdEvent": "STALL_SLOT_FRONTEND" - }, - { - "ArchStdEvent": "STALL_SLOT" - }, - { - "ArchStdEvent": "STALL_BACKEND_MEM" - } -]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/retired.json new file +30 -0
@@ -0,0 +1,30 @@ +[ + { + "ArchStdEvent": "SW_INCR", + "PublicDescription": "Counts software writes to the PMSWINC_EL0 (software PMU increment) register. The PMSWINC_EL0 register is a manually updated counter for use by application software.\n\nThis event could be used to measure any user program event, such as accesses to a particular data structure (by writing to the PMSWINC_EL0 register each time the data structure is accessed).\n\nTo use the PMSWINC_EL0 register and event, developers must insert instructions that write to the PMSWINC_EL0 register into the source code.\n\nSince the SW_INCR event records writes to the PMSWINC_EL0 register, there is no need to do a read/increment/write sequence to the PMSWINC_EL0 register." + }, + { + "ArchStdEvent": "INST_RETIRED", + "PublicDescription": "Counts instructions that have been architecturally executed." + }, + { + "ArchStdEvent": "CID_WRITE_RETIRED", + "PublicDescription": "Counts architecturally executed writes to the CONTEXTIDR register, which usually contain the kernel PID and can be output with hardware trace." + }, + { + "ArchStdEvent": "TTBR_WRITE_RETIRED", + "PublicDescription": "Counts architectural writes to TTBR0/1_EL1. If virtualization host extensions are enabled (by setting the HCR_EL2.E2H bit to 1), then accesses to TTBR0/1_EL1 that are redirected to TTBR0/1_EL2, or accesses to TTBR0/1_EL12, are counted. TTBRn registers are typically updated when the kernel is swapping user-space threads or applications." + }, + { + "ArchStdEvent": "BR_RETIRED", + "PublicDescription": "Counts architecturally executed branches, whether the branch is taken or not. Instructions that explicitly write to the PC are also counted." + }, + { + "ArchStdEvent": "BR_MIS_PRED_RETIRED", + "PublicDescription": "Counts branches counted by BR_RETIRED which were mispredicted and caused a pipeline flush." + }, + { + "ArchStdEvent": "OP_RETIRED", + "PublicDescription": "Counts micro-operations that are architecturally executed. This is a count of number of micro-operations retired from the commit queue in a single cycle." + } +]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/spe.json +8 -4
@@ -1,14 +1,18 @@ [ { - "ArchStdEvent": "SAMPLE_POP" + "ArchStdEvent": "SAMPLE_POP", + "PublicDescription": "Counts statistical profiling sample population, the count of all operations that could be sampled but may or may not be chosen for sampling." }, { - "ArchStdEvent": "SAMPLE_FEED" + "ArchStdEvent": "SAMPLE_FEED", + "PublicDescription": "Counts statistical profiling samples taken for sampling." }, { - "ArchStdEvent": "SAMPLE_FILTRATE" + "ArchStdEvent": "SAMPLE_FILTRATE", + "PublicDescription": "Counts statistical profiling samples taken which are not removed by filtering." }, { - "ArchStdEvent": "SAMPLE_COLLISION" + "ArchStdEvent": "SAMPLE_COLLISION", + "PublicDescription": "Counts statistical profiling samples that have collided with a previous sample and so therefore not taken." } ]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/spec_operation.json new file +110 -0
110 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/stall.json new file +30 -0
@@ -0,0 +1,30 @@ +[ + { + "ArchStdEvent": "STALL_FRONTEND", + "PublicDescription": "Counts cycles when frontend could not send any micro-operations to the rename stage because of frontend resource stalls caused by fetch memory latency or branch prediction flow stalls. All the frontend slots were empty during the cycle when this event counts." + }, + { + "ArchStdEvent": "STALL_BACKEND", + "PublicDescription": "Counts cycles whenever the rename unit is unable to send any micro-operations to the backend of the pipeline because of backend resource constraints. Backend resource constraints can include issue stage fullness, execution stage fullness, or other internal pipeline resource fullness. All the backend slots were empty during the cycle when this event counts." + }, + { + "ArchStdEvent": "STALL", + "PublicDescription": "Counts cycles when no operations are sent to the rename unit from the frontend or from the rename unit to the backend for any reason (either frontend or backend stall)." + }, + { + "ArchStdEvent": "STALL_SLOT_BACKEND", + "PublicDescription": "Counts slots per cycle in which no operations are sent from the rename unit to the backend due to backend resource constraints." + }, + { + "ArchStdEvent": "STALL_SLOT_FRONTEND", + "PublicDescription": "Counts slots per cycle in which no operations are sent to the rename unit from the frontend due to frontend resource constraints." + }, + { + "ArchStdEvent": "STALL_SLOT", + "PublicDescription": "Counts slots per cycle in which no operations are sent to the rename unit from the frontend or from the rename unit to the backend for any reason (either frontend or backend stall)." + }, + { + "ArchStdEvent": "STALL_BACKEND_MEM", + "PublicDescription": "Counts cycles when the backend is stalled because there is a pending demand load request in progress in the last level core cache." + } +]
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/sve.json new file +50 -0
50 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/tlb.json new file +66 -0
66 lines not on this page · raw message
tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/trace.json +18 -9
@@ -1,29 +1,38 @@ [ { - "ArchStdEvent": "TRB_WRAP" + "ArchStdEvent": "TRB_WRAP", + "PublicDescription": "This event is generated each time the current write pointer is wrapped to the base pointer." }, { - "ArchStdEvent": "TRCEXTOUT0" + "ArchStdEvent": "TRCEXTOUT0", + "PublicDescription": "This event is generated each time an event is signaled by ETE external event 0." }, { - "ArchStdEvent": "TRCEXTOUT1" + "ArchStdEvent": "TRCEXTOUT1", + "PublicDescription": "This event is generated each time an event is signaled by ETE external event 1." }, { - "ArchStdEvent": "TRCEXTOUT2" + "ArchStdEvent": "TRCEXTOUT2", + "PublicDescription": "This event is generated each time an event is signaled by ETE external event 2." }, { - "ArchStdEvent": "TRCEXTOUT3" + "ArchStdEvent": "TRCEXTOUT3", + "PublicDescription": "This event is generated each time an event is signaled by ETE external event 3." }, { - "ArchStdEvent": "CTI_TRIGOUT4" + "ArchStdEvent": "CTI_TRIGOUT4", + "PublicDescription": "This event is generated each time an event is signaled on CTI output trigger 4." }, { - "ArchStdEvent": "CTI_TRIGOUT5" + "ArchStdEvent": "CTI_TRIGOUT5", + "PublicDescription": "This event is generated each time an event is signaled on CTI output trigger 5." }, { - "ArchStdEvent": "CTI_TRIGOUT6" + "ArchStdEvent": "CTI_TRIGOUT6", + "PublicDescription": "This event is generated each time an event is signaled on CTI output trigger 6." }, { - "ArchStdEvent": "CTI_TRIGOUT7" + "ArchStdEvent": "CTI_TRIGOUT7", + "PublicDescription": "This event is generated each time an event is signaled on CTI output trigger 7." } ]
Signature · 1 line
2.34.1