From: Ilkka Koskinen <ilkka@os.amperecomputing.com>
To: John Garry <john.g.garry@oracle.com>,
Will Deacon <will@kernel.org>, James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org
Subject: [PATCH 0/3] perf vendor events arm64: Add AmpereOneX events and metrics and fix AmpereOne bugs
Date: Thu, 30 Nov 2023 18:15:47 -0800 [thread overview]
Message-ID: <20231201021550.1109196-1-ilkka@os.amperecomputing.com> (raw)
Add support for AmpereOneX Core PMU events. In addition, fix typo in
GPC_FLUSH_MEM_FAULT's name and add missing DefaultMetricgroupName to
metrics.
Ilkka Koskinen (3):
perf vendor events arm64: AmpereOne: Add missing
DefaultMetricgroupName fields
perf vendor events arm64: AmpereOne: Rename BPU_FLUSH_MEM_FAULT to
GPC_FLUSH_MEM_FAULT
perf vendor events arm64: AmpereOneX: Add core PMU events and metrics
.../arm64/ampere/ampereone/core-imp-def.json | 2 +-
.../arch/arm64/ampere/ampereone/metrics.json | 2 +
.../arch/arm64/ampere/ampereonex/branch.json | 125 +++++
.../arch/arm64/ampere/ampereonex/bus.json | 20 +
.../arch/arm64/ampere/ampereonex/cache.json | 206 ++++++++
.../arm64/ampere/ampereonex/core-imp-def.json | 464 ++++++++++++++++++
.../arm64/ampere/ampereonex/exception.json | 47 ++
.../arm64/ampere/ampereonex/instruction.json | 128 +++++
.../arm64/ampere/ampereonex/intrinsic.json | 14 +
.../arch/arm64/ampere/ampereonex/memory.json | 41 ++
.../arch/arm64/ampere/ampereonex/metrics.json | 442 +++++++++++++++++
.../arch/arm64/ampere/ampereonex/mmu.json | 170 +++++++
.../arm64/ampere/ampereonex/pipeline.json | 41 ++
.../arch/arm64/ampere/ampereonex/spe.json | 14 +
tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 +
15 files changed, 1716 insertions(+), 1 deletion(-)
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/branch.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/bus.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/cache.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/core-imp-def.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/exception.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/instruction.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/intrinsic.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/memory.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/mmu.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/pipeline.json
create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/ampereonex/spe.json
--
2.41.0
next reply other threads:[~2023-12-01 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 2:15 Ilkka Koskinen [this message]
2023-12-01 2:15 ` [PATCH 1/3] perf vendor events arm64: AmpereOne: Add missing DefaultMetricgroupName fields Ilkka Koskinen
2023-12-04 19:02 ` Ian Rogers
2023-12-04 19:41 ` Arnaldo Carvalho de Melo
2023-12-01 2:15 ` [PATCH 2/3] perf vendor events arm64: AmpereOne: Rename BPU_FLUSH_MEM_FAULT to GPC_FLUSH_MEM_FAULT Ilkka Koskinen
2023-12-04 19:03 ` Ian Rogers
2023-12-01 2:15 ` [PATCH 3/3] perf vendor events arm64: AmpereOneX: Add core PMU events and metrics Ilkka Koskinen
2023-12-04 19:07 ` Ian Rogers
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=20231201021550.1109196-1-ilkka@os.amperecomputing.com \
--to=ilkka@os.amperecomputing.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox