From: James Clark <James.Clark@arm.com>
To: "linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: nd <nd@arm.com>, James Clark <James.Clark@arm.com>
Subject: [PATCH v2 0/1] perf tools: Add PMU event JSON files for ARM Cortex-A76 and, Neoverse N1.
Date: Mon, 2 Sep 2019 16:08:13 +0000 [thread overview]
Message-ID: <20190902160713.1425-1-james.clark@arm.com> (raw)
In-Reply-To: <00f00310-09ae-909c-4dfd-021996e45be1@arm.com>
Resubmitting due to the previous patch having a disclaimer appended.
I've tested that this applies cleanly with git am.
James Clark (1):
perf tools: Add PMU event JSON files for ARM Cortex-A76 and, Neoverse
N1.
.../arch/arm64/arm/cortex-a76-n1/branch.json | 14 ++
.../arch/arm64/arm/cortex-a76-n1/bus.json | 24 ++
.../arch/arm64/arm/cortex-a76-n1/cache.json | 207 ++++++++++++++++++
.../arm64/arm/cortex-a76-n1/exception.json | 52 +++++
.../arm64/arm/cortex-a76-n1/instruction.json | 108 +++++++++
.../arch/arm64/arm/cortex-a76-n1/memory.json | 23 ++
.../arch/arm64/arm/cortex-a76-n1/other.json | 7 +
.../arm64/arm/cortex-a76-n1/pipeline.json | 14 ++
tools/perf/pmu-events/arch/arm64/mapfile.csv | 2 +
9 files changed, 451 insertions(+)
create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/branch.json
create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/bus.json
create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/cache.json
create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/exception.json
create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/instruction.json
create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/memory.json
create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/other.json
create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/pipeline.json
--
2.23.0
next prev parent reply other threads:[~2019-09-02 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 13:19 [PATCH " James Clark
2019-07-26 13:24 ` [PATCH 1/1] " James Clark
2019-07-26 13:40 ` James Clark
2019-09-02 16:08 ` James Clark [this message]
2019-09-02 16:08 ` [PATCH v2 " James Clark
2019-09-20 16:21 ` [tip: perf/urgent] " tip-bot2 for James Clark
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=20190902160713.1425-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=nd@arm.com \
/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
all inboxes | Powered by JetHome®