lkml.org 
[lkml]   [2022]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] perf vendor events: Update events for Neoverse E1
From

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

\
 
 \ /
  Last update: 2022-09-12 19:14    [W:0.069 / U:1.324 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site