From: Nick Forrington <nick.forrington@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
John Garry <john.garry@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
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] perf vendor events: Update events for Neoverse E1
Date: Mon, 12 Sep 2022 18:13:39 +0100 [thread overview]
Message-ID: <c8af4295-0e28-d205-3220-f3e00ab509de@arm.com> (raw)
In-Reply-To: <Yxo2ZSKtne7E/2Sn@kernel.org>
On 08/09/2022 19:37, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 06, 2022 at 02:22:54PM +0100, John Garry escreveu:
>> On 06/09/2022 14:07, Arnaldo Carvalho de Melo wrote:
>>> Em Mon, Sep 05, 2022 at 04:30:19PM +0100, Nick Forrington escreveu:
>>>> Based on updated data from:
>>>> https://github.com/ARM-software/data/blob/master/pmu/neoverse-e1.json
>>>>
>>>> which is based on PMU event descriptions from the Arm Neoverse E1
>>>> Technical Reference Manual.
>>>>
>>>> This includes additional implementation defined fields not previously
>>>> included, and removes unimplemented events related to Arm's Statistical
>>>> Profiling Extension (SPE).
>>> Applied locally, would be good to have an Acked-by or Reviewed-by, John?
>> Regardless of comment, below:
>> Reviewed-by: John Garry <john.garry@huawei.com>
> So, I removed this one, applied v2, now trying to apply the other patch
> from Nick, the one moving some events to a different file, but not being
> able to:
>
> ⬢[acme@toolbox perf]$ b4 am -ctsl --cc-trailers 39abfee9-4a9b-ec44-9b02-a6cd34cfe64d@huawei.com
> Grabbing thread from lore.kernel.org/all/39abfee9-4a9b-ec44-9b02-a6cd34cfe64d%40huawei.com/t.mbox.gz
> Checking for newer revisions on https://lore.kernel.org/all/
> Analyzing 3 messages in the thread
> Checking attestation on all messages, may take a moment...
> ---
> [PATCH] perf vendor events arm64: Move REMOTE_ACCESS to "memory" category
> + Reviewed-by: John Garry <john.garry@huawei.com>
> ---
> Total patches: 1
> ---
> Link: https://lore.kernel.org/r/20220908112519.64614-1-nick.forrington@arm.com
> Base: not specified
> git am ./20220908_nick_forrington_perf_vendor_events_arm64_move_remote_access_to_memory_category.mbx
> ⬢[acme@toolbox perf]$ git am ./20220908_nick_forrington_perf_vendor_events_arm64_move_remote_access_to_memory_category.mbx
> Applying: perf vendor events arm64: Move REMOTE_ACCESS to "memory" category
> error: patch failed: tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/memory.json:3
> error: tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/memory.json: patch does not apply
> error: tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/other.json: does not exist in index
> error: patch failed: tools/perf/pmu-events/arch/arm64/arm/neoverse-n2/memory.json:2
> error: tools/perf/pmu-events/arch/arm64/arm/neoverse-n2/memory.json: patch does not apply
> error: tools/perf/pmu-events/arch/arm64/arm/neoverse-n2/other.json: does not exist in index
> error: patch failed: tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/memory.json:2
> error: tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/memory.json: patch does not apply
> error: tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/other.json: does not exist in index
> Patch failed at 0001 perf vendor events arm64: Move REMOTE_ACCESS to "memory" category
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> ⬢[acme@toolbox perf]$
I think this was already applied via
1081fb0f6d6e68186e1088db33396b11770a0710
All 3 patches appear to be present.
Thanks, Nick
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-12 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 15:30 [PATCH] perf vendor events: Update events for Neoverse E1 Nick Forrington
2022-09-06 13:07 ` Arnaldo Carvalho de Melo
2022-09-06 13:22 ` John Garry
2022-09-06 14:36 ` Robin Murphy
2022-09-06 14:47 ` John Garry
2022-09-07 15:39 ` Nick Forrington
2022-09-08 18:37 ` Arnaldo Carvalho de Melo
2022-09-12 17:13 ` Nick Forrington [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=c8af4295-0e28-d205-3220-f3e00ab509de@arm.com \
--to=nick.forrington@arm.com \
--cc=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=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).