linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Clark <james.clark@linaro.org>
To: Yangyu Chen <cyy@cyyself.name>,
	Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org,
	John Garry <john.g.garry@oracle.com>,
	Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
	Leo Yan <leo.yan@linux.dev>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Liang Kan <kan.liang@linux.intel.com>,
	Yoshihiro Furudera <fj5100bi@fujitsu.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] perf vendor events arm64: Add A720/A520 events/metrics
Date: Fri, 14 Feb 2025 10:02:44 +0000	[thread overview]
Message-ID: <1b8b234f-6435-45cf-83e7-8e86c84f075f@linaro.org> (raw)
In-Reply-To: <tencent_45B4E91CA370C563D6420A1A25F992056D09@qq.com>



On 14/02/2025 5:49 am, Yangyu Chen wrote:
> 
> 
>> On 14 Feb 2025, at 09:12, Namhyung Kim <namhyung@kernel.org> wrote:
>>
>> Hello,
>>
>> On Thu, Feb 13, 2025 at 11:11:01PM +0800, Yangyu Chen wrote:
>>> This patchset adds the perf JSON files for the Cortex-A720 and Cortex-A520
>>> processors. Some events have been tested on Raxda Orion 6 with Cix P1 SoC
>>> (8xA720 + 4xA520) running mainline Kernel with ACPI mode.
>>
>> I'm curious how the name of PMUs look like.  It is cortex_a720 (or a520)?
> 
> The name of PMUs comes from Arm's documentation. I have included these
> links in each patch.
> 
>> I remember there's a logic to check the length of hex digits at the end.
>>
> 
> Could you provide more details about this?
> 
>> Ian, are you ok with this?
>>

I think they wouldn't be merged because they're core PMUs, so should be 
fine? Even though they would otherwise be merged because they're more 
than 3 hex digits.

>> Thanks,
>> Namhyung
>>
>>>
>>> Yangyu Chen (2):
>>>   perf vendor events arm64: Add Cortex-A720 events/metrics
>>>   perf vendor events arm64: Add Cortex-A520 events/metrics
>>>
>>> .../arch/arm64/arm/cortex-a520/bus.json       |  26 ++
>>> .../arch/arm64/arm/cortex-a520/exception.json |  18 +
>>> .../arm64/arm/cortex-a520/fp_operation.json   |  14 +
>>> .../arch/arm64/arm/cortex-a520/general.json   |   6 +
>>> .../arch/arm64/arm/cortex-a520/l1d_cache.json |  50 ++
>>> .../arch/arm64/arm/cortex-a520/l1i_cache.json |  14 +
>>> .../arch/arm64/arm/cortex-a520/l2_cache.json  |  46 ++
>>> .../arch/arm64/arm/cortex-a520/l3_cache.json  |  21 +
>>> .../arch/arm64/arm/cortex-a520/ll_cache.json  |  10 +
>>> .../arch/arm64/arm/cortex-a520/memory.json    |  58 +++
>>> .../arch/arm64/arm/cortex-a520/metrics.json   | 373 +++++++++++++++
>>> .../arch/arm64/arm/cortex-a520/pmu.json       |   8 +
>>> .../arch/arm64/arm/cortex-a520/retired.json   |  90 ++++
>>> .../arm64/arm/cortex-a520/spec_operation.json |  70 +++
>>> .../arch/arm64/arm/cortex-a520/stall.json     |  82 ++++
>>> .../arch/arm64/arm/cortex-a520/sve.json       |  22 +
>>> .../arch/arm64/arm/cortex-a520/tlb.json       |  78 ++++
>>> .../arch/arm64/arm/cortex-a520/trace.json     |  32 ++
>>> .../arch/arm64/arm/cortex-a720/bus.json       |  18 +
>>> .../arch/arm64/arm/cortex-a720/exception.json |  62 +++
>>> .../arm64/arm/cortex-a720/fp_operation.json   |  22 +
>>> .../arch/arm64/arm/cortex-a720/general.json   |  10 +
>>> .../arch/arm64/arm/cortex-a720/l1d_cache.json |  50 ++
>>> .../arch/arm64/arm/cortex-a720/l1i_cache.json |  14 +
>>> .../arch/arm64/arm/cortex-a720/l2_cache.json  |  62 +++
>>> .../arch/arm64/arm/cortex-a720/l3_cache.json  |  22 +
>>> .../arch/arm64/arm/cortex-a720/ll_cache.json  |  10 +
>>> .../arch/arm64/arm/cortex-a720/memory.json    |  54 +++
>>> .../arch/arm64/arm/cortex-a720/metrics.json   | 436 ++++++++++++++++++
>>> .../arch/arm64/arm/cortex-a720/pmu.json       |   8 +
>>> .../arch/arm64/arm/cortex-a720/retired.json   |  90 ++++
>>> .../arch/arm64/arm/cortex-a720/spe.json       |  42 ++
>>> .../arm64/arm/cortex-a720/spec_operation.json |  90 ++++
>>> .../arch/arm64/arm/cortex-a720/stall.json     |  82 ++++
>>> .../arch/arm64/arm/cortex-a720/sve.json       |  50 ++
>>> .../arch/arm64/arm/cortex-a720/tlb.json       |  74 +++
>>> .../arch/arm64/arm/cortex-a720/trace.json     |  32 ++
>>> .../arch/arm64/common-and-microarch.json      |  15 +
>>> tools/perf/pmu-events/arch/arm64/mapfile.csv  |   2 +
>>> 39 files changed, 2263 insertions(+)
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/bus.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/exception.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/fp_operation.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/general.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/l1d_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/l1i_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/l2_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/l3_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/ll_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/memory.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/metrics.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/pmu.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/retired.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/spec_operation.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/stall.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/sve.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/tlb.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a520/trace.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/bus.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/exception.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/fp_operation.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/general.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/l1d_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/l1i_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/l2_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/l3_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/ll_cache.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/memory.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/metrics.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/pmu.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/retired.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/spe.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/spec_operation.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/stall.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/sve.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/tlb.json
>>> create mode 100644 tools/perf/pmu-events/arch/arm64/arm/cortex-a720/trace.json
>>>
>>> -- 
>>> 2.47.2
>>>
> 


  reply	other threads:[~2025-02-14 10:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 15:11 [PATCH 0/2] perf vendor events arm64: Add A720/A520 events/metrics Yangyu Chen
2025-02-13 15:12 ` [PATCH 1/2] perf vendor events arm64: Add Cortex-A720 events/metrics Yangyu Chen
2025-02-13 16:49   ` Ian Rogers
2025-02-13 15:12 ` [PATCH 2/2] perf vendor events arm64: Add Cortex-A520 events/metrics Yangyu Chen
2025-02-13 16:53   ` Ian Rogers
2025-02-14  1:12 ` [PATCH 0/2] perf vendor events arm64: Add A720/A520 events/metrics Namhyung Kim
2025-02-14  5:49   ` Yangyu Chen
2025-02-14 10:02     ` James Clark [this message]
2025-02-18  0:41       ` Ian Rogers
2025-02-18  9:30         ` James Clark
2025-02-18 22:19           ` Namhyung Kim
2025-02-18 22:33             ` Ian Rogers
2025-02-19 15:25               ` James Clark
2025-02-19 18:37                 ` Ian Rogers
2025-02-20  3:37               ` Yangyu Chen
     [not found]               ` <tencent_EDA4AFD185EF51104EDBCEB109D720862B05@qq.com>
2025-02-20 14:37                 ` 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=1b8b234f-6435-45cf-83e7-8e86c84f075f@linaro.org \
    --to=james.clark@linaro.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=cyy@cyyself.name \
    --cc=fj5100bi@fujitsu.com \
    --cc=irogers@google.com \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=leo.yan@linux.dev \
    --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=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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).