From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Nick Forrington <nick.forrington@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] perf vendor events: Add missing Neoverse V1 events
Date: Mon, 5 Sep 2022 17:26:24 -0300 [thread overview]
Message-ID: <YxZbcOv7OcKO8SYs@kernel.org> (raw)
In-Reply-To: <20220905114024.7552-1-nick.forrington@arm.com>
Em Mon, Sep 05, 2022 at 12:40:24PM +0100, Nick Forrington escreveu:
> Based on updated data from:
> https://github.com/ARM-software/data/blob/master/pmu/neoverse-v1.json
>
> which is based on PMU event descriptions from the Arm Neoverse V1
> Technical Reference Manual.
>
> This adds the following missing events:
> ASE_INST_SPEC
> SVE_INST_SPEC
> SVE_PRED_SPEC
> SVE_PRED_EMPTY_SPEC
> SVE_PRED_FULL_SPEC
> SVE_PRED_PARTIAL_SPEC
> SVE_LDFF_SPEC
> SVE_LDFF_FAULT_SPEC
> FP_SCALE_OPS_SPEC
> FP_FIXED_OPS_SPEC
>
> Reviewed-by: John Garry <john.garry@huawei.com>
> Signed-off-by: Nick Forrington <nick.forrington@arm.com>
Thanks, applied.
- Arnaldo
> ---
> V1 -> V2: Remove REMOTE_ACCESS re-categorisation (to be submitted
> separately)
> .../arm64/arm/neoverse-v1/instruction.json | 30 +++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/instruction.json b/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/instruction.json
> index 25825e14c535..e29b88fb7f24 100644
> --- a/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/instruction.json
> +++ b/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/instruction.json
> @@ -85,5 +85,35 @@
> },
> {
> "ArchStdEvent": "RC_ST_SPEC"
> + },
> + {
> + "ArchStdEvent": "ASE_INST_SPEC"
> + },
> + {
> + "ArchStdEvent": "SVE_INST_SPEC"
> + },
> + {
> + "ArchStdEvent": "SVE_PRED_SPEC"
> + },
> + {
> + "ArchStdEvent": "SVE_PRED_EMPTY_SPEC"
> + },
> + {
> + "ArchStdEvent": "SVE_PRED_FULL_SPEC"
> + },
> + {
> + "ArchStdEvent": "SVE_PRED_PARTIAL_SPEC"
> + },
> + {
> + "ArchStdEvent": "SVE_LDFF_SPEC"
> + },
> + {
> + "ArchStdEvent": "SVE_LDFF_FAULT_SPEC"
> + },
> + {
> + "ArchStdEvent": "FP_SCALE_OPS_SPEC"
> + },
> + {
> + "ArchStdEvent": "FP_FIXED_OPS_SPEC"
> }
> ]
> --
> 2.25.1
--
- Arnaldo
prev parent reply other threads:[~2022-09-05 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 11:40 [PATCH v2] perf vendor events: Add missing Neoverse V1 events Nick Forrington
2022-09-05 20:26 ` Arnaldo Carvalho de Melo [this message]
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=YxZbcOv7OcKO8SYs@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.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=namhyung@kernel.org \
--cc=nick.forrington@arm.com \
--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).