linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Clark <james.clark@arm.com>
To: linux-perf-users@vger.kernel.org
Cc: James Clark <james.clark@arm.com>,
	John Garry <john.g.garry@oracle.com>,
	Will Deacon <will@kernel.org>, 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>,
	Nick Forrington <nick.forrington@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] perf vendor events arm64: Update V1 events using Arm telemetry repo
Date: Thu, 31 Aug 2023 17:15:30 +0100	[thread overview]
Message-ID: <20230831161618.134738-1-james.clark@arm.com> (raw)

This is the last set of JSON updates using the Arm telemetry repo. Perf
now has an up to date copy of everything that is currently published
there. Future updates will be done as new data becomes available.

James Clark (2):
  perf vendor events arm64: Update V1 events using Arm telemetry repo
  perf vendor events arm64: Add V1 metrics using Arm telemetry repo

 .../arch/arm64/arm/neoverse-v1/branch.json    |   8 -
 .../arch/arm64/arm/neoverse-v1/bus.json       |  18 +-
 .../arch/arm64/arm/neoverse-v1/cache.json     | 155 ------------
 .../arch/arm64/arm/neoverse-v1/exception.json |  45 ++--
 .../arm64/arm/neoverse-v1/fp_operation.json   |  10 +
 .../arch/arm64/arm/neoverse-v1/general.json   |  10 +
 .../arm64/arm/neoverse-v1/instruction.json    | 119 ---------
 .../arch/arm64/arm/neoverse-v1/l1d_cache.json |  54 ++++
 .../arch/arm64/arm/neoverse-v1/l1i_cache.json |  14 ++
 .../arch/arm64/arm/neoverse-v1/l2_cache.json  |  50 ++++
 .../arch/arm64/arm/neoverse-v1/l3_cache.json  |  22 ++
 .../arch/arm64/arm/neoverse-v1/ll_cache.json  |  10 +
 .../arch/arm64/arm/neoverse-v1/memory.json    |  21 +-
 .../arch/arm64/arm/neoverse-v1/metrics.json   | 233 ++++++++++++++++++
 .../arch/arm64/arm/neoverse-v1/pipeline.json  |  23 --
 .../arch/arm64/arm/neoverse-v1/retired.json   |  30 +++
 .../arch/arm64/arm/neoverse-v1/spe.json       |  18 ++
 .../arm64/arm/neoverse-v1/spec_operation.json | 110 +++++++++
 .../arch/arm64/arm/neoverse-v1/stall.json     |  30 +++
 .../arch/arm64/arm/neoverse-v1/sve.json       |  30 +++
 .../arch/arm64/arm/neoverse-v1/tlb.json       |  66 +++++
 21 files changed, 735 insertions(+), 341 deletions(-)
 delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/branch.json
 delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/cache.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/fp_operation.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/general.json
 delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/instruction.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/l1d_cache.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/l1i_cache.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/l2_cache.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/l3_cache.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/ll_cache.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/metrics.json
 delete mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/pipeline.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/retired.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/spe.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/spec_operation.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/stall.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/sve.json
 create mode 100644 tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/tlb.json

-- 
2.34.1


             reply	other threads:[~2023-08-31 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 16:15 James Clark [this message]
2023-08-31 16:15 ` [PATCH 1/2] perf vendor events arm64: Update V1 events using Arm telemetry repo James Clark
2023-08-31 16:15 ` [PATCH 2/2] perf vendor events arm64: Add V1 metrics " James Clark
2023-09-12 19:34 ` [PATCH 0/2] perf vendor events arm64: Update V1 events " Arnaldo Carvalho de Melo

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=20230831161618.134738-1-james.clark@arm.com \
    --to=james.clark@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.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=nick.forrington@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).