Messages in this thread | | | Date | Fri, 21 Oct 2022 11:59:27 +0100 | Subject | Re: [PATCH] perf vendor events: Add Arm Neoverse V2 PMU events | From | James Clark <> |
| |
On 21/10/2022 11:47, John Garry wrote: > On 20/10/2022 14:45, James Clark wrote: >> Rename the neoverse-n2 folder to make it clear that it includes V2, and >> add V2 to mapfile.csv. V2 has the same events as N2, visible by running >> the following command in the ARM-software/data github repo [1]: >> >> diff pmu/neoverse-v2.json pmu/neoverse-n2.json | grep code >> >> Testing: >> >> $ perf test pmu >> >> 10: PMU events : >> 10.1: PMU event table sanity : Ok >> 10.2: PMU event map aliases : Ok >> 10.3: Parsing of PMU event table metrics : Ok >> 10.4: Parsing of PMU event table metrics with fake PMUs : Ok >> >> [1]:https://github.com/ARM-software/data >> >> Signed-off-by: James Clark<james.clark@arm.com> >> --- > > This looks ok. Out of curiosity, do you know how the naming works for > these neoverse cores? Were "n" a predecessor to "v"?
Thanks for the review. No, they're more like different product lines than predecessors. From the image on this article [1], N are focused on performance per watt and V are high performance.
[1]: https://www.arm.com/company/news/2022/09/redefining-the-global-computing-infrastructure-with-next-generation-arm-neoverse-platforms
> > thanks, > John
| |