From: Jing Zhang <renyu.zj@linux.alibaba.com>
To: Shuai Xue <xueshuai@linux.alibaba.com>,
John Garry <john.g.garry@oracle.com>,
Ian Rogers <irogers@google.com>, Will Deacon <will@kernel.org>
Cc: James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org,
Zhuo Song <zhuo.song@linux.alibaba.com>
Subject: Re: [PATCH v2 4/5] perf jevents: Add support for Yitian 710 DDR PMU aliasing
Date: Mon, 8 May 2023 19:39:05 +0800 [thread overview]
Message-ID: <9f01bb3c-2f90-0784-d1ee-ff2ebcd92b1b@linux.alibaba.com> (raw)
In-Reply-To: <6ca986e4-38a0-4296-5307-e6e344c62853@linux.alibaba.com>
在 2023/5/4 下午3:18, Shuai Xue 写道:
>
>
> On 2023/4/24 17:44, Jing Zhang wrote:
>> Add support for T-HEAD Yitian 710 SoC DDR PMU aliasing.
>>
>> Signed-off-by: Jing Zhang <renyu.zj@linux.alibaba.com>
>> ---
>> .../arm64/freescale/yitian710/sys/ali_drw.json | 373 +++++++++++++++++++++
>> tools/perf/pmu-events/jevents.py | 1 +
>> 2 files changed, 374 insertions(+)
>> create mode 100644 tools/perf/pmu-events/arch/arm64/freescale/yitian710/sys/ali_drw.json
>>
>> diff --git a/tools/perf/pmu-events/arch/arm64/freescale/yitian710/sys/ali_drw.json b/tools/perf/pmu-events/arch/arm64/freescale/yitian710/sys/ali_drw.json
>> new file mode 100644
>> index 0000000..f17f239
>> --- /dev/null
>> +++ b/tools/perf/pmu-events/arch/arm64/freescale/yitian710/sys/ali_drw.json
>> @@ -0,0 +1,373 @@
>> +[
>> + {
>> + "BriefDescription": "A Write or Read Op at HIF interface. 64B",
>> + "ConfigCode": "0x0",
>> + "EventName": "hif_rd_or_wr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Write Op at HIF interface. 64B",
>> + "ConfigCode": "0x1",
>> + "EventName": "hif_wr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Read Op at HIF interface. 64B",
>> + "ConfigCode": "0x2",
>> + "EventName": "hif_rd",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Read-Modify-Write Op at HIF interface. 64B",
>> + "ConfigCode": "0x3",
>> + "EventName": "hif_rmw",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A high priority Read at HIF interface. 64B",
>> + "ConfigCode": "0x4",
>> + "EventName": "hif_hi_pri_rd",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A write data cycle at DFI interface (to DRAM)",
>
> Add an ending period to BriefDescription as you do latter.
>
Ok.
>> + "ConfigCode": "0x7",
>> + "EventName": "dfi_wr_data_cycles",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A read data cycle at DFI interface (to DRAM).",
>> + "ConfigCode": "0x8",
>> + "EventName": "dfi_rd_data_cycles",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A high priority read becomes critical.",
>> + "ConfigCode": "0x9",
>> + "EventName": "hpr_xact_when_critical",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A low priority read becomes critical.",
>> + "ConfigCode": "0xA",
>> + "EventName": "lpr_xact_when_critical",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A write becomes critical.",
>> + "ConfigCode": "0xB",
>> + "EventName": "wr_xact_when_critical",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "An Activate (ACT) command to DRAM.",
>> + "ConfigCode": "0xC",
>> + "EventName": "op_is_activate",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Read or Write CAS command to DRAM.",
>> + "ConfigCode": "0xD",
>> + "EventName": "op_is_rd_or_wr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "An ACT command for read to DRAM.",
>> + "ConfigCode": "0xE",
>> + "EventName": "op_is_rd_activate",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Read CAS command to DRAM.",
>> + "ConfigCode": "0xF",
>> + "EventName": "op_is_rd",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Write CAS command to DRAM.",
>> + "ConfigCode": "0x10",
>> + "EventName": "op_is_wr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Masked Write command to DRAM.",
>> + "ConfigCode": "0x11",
>> + "EventName": "op_is_mwr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Precharge (PRE) command to DRAM.",
>> + "ConfigCode": "0x12",
>> + "EventName": "op_is_precharge",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A PRE required by read or write.",
>
> A non-abbreviation format is prefered here.
>
Ok.
>> + "ConfigCode": "0x13",
>> + "EventName": "precharge_for_rdwr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A PRE required by other conditions.",
>> + "ConfigCode": "0x14",
>> + "EventName": "precharge_for_other",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A read-write turnaround.",
>> + "ConfigCode": "0x15",
>> + "EventName": "rdwr_transitions",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A write combine (merge) in write data buffer.",
>> + "ConfigCode": "0x16",
>> + "EventName": "write_combine",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Write-After-Read hazard.",
>> + "ConfigCode": "0x17",
>> + "EventName": "war_hazard",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Read-After-Write hazard.",
>> + "ConfigCode": "0x18",
>> + "EventName": "raw_hazard",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A Write-After-Write hazard.",
>> + "ConfigCode": "0x19",
>> + "EventName": "waw_hazard",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "Rank0 enters self-refresh (SRE).",
>> + "ConfigCode": "0x1A",
>> + "EventName": "op_is_enter_selfref_rk0",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "Rank1 enters self-refresh (SRE).",
>> + "ConfigCode": "0x1B",
>> + "EventName": "op_is_enter_selfref_rk1",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "Rank2 enters self-refresh (SRE).",
>> + "ConfigCode": "0x1C",
>> + "EventName": "op_is_enter_selfref_rk2",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "Rank3 enters self-refresh (SRE).",
>> + "ConfigCode": "0x1D",
>> + "EventName": "op_is_enter_selfref_rk3",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "Rank0 enters power-down (PDE).",
>> + "ConfigCode": "0x1E",
>> + "EventName": "op_is_enter_powerdown_rk0",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "Rank1 enters power-down (PDE).",
>> + "ConfigCode": "0x1F",
>> + "EventName": "op_is_enter_powerdown_rk1",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "Rank2 enters power-down (PDE).",
>> + "ConfigCode": "0x20",
>> + "EventName": "op_is_enter_powerdown_rk2",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "Rank3 enters power-down (PDE).",
>> + "ConfigCode": "0x21",
>> + "EventName": "op_is_enter_powerdown_rk3",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A cycle that Rank0 stays in self-refresh mode.",
>> + "ConfigCode": "0x26",
>> + "EventName": "selfref_mode_rk0",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A cycle that Rank1 stays in self-refresh mode.",
>> + "ConfigCode": "0x27",
>> + "EventName": "selfref_mode_rk1",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A cycle that Rank2 stays in self-refresh mode.",
>> + "ConfigCode": "0x28",
>> + "EventName": "selfref_mode_rk2",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A cycle that Rank3 stays in self-refresh mode.",
>> + "ConfigCode": "0x29",
>> + "EventName": "selfref_mode_rk3",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "An auto-refresh (REF) command to DRAM.",
>> + "ConfigCode": "0x2A",
>> + "EventName": "op_is_refresh",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A critical REF command to DRAM.",
>> + "ConfigCode": "0x2B",
>> + "EventName": "op_is_crit_ref",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "An MRR or MRW command to DRAM.",
>> + "ConfigCode": "0x2D",
>> + "EventName": "op_is_load_mode",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A ZQCal command to DRAM.",
>> + "ConfigCode": "0x2E",
>> + "EventName": "op_is_zqcl",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "At least one entry in read queue reaches the visible window limit.",
>> + "ConfigCode": "0x30",
>> + "EventName": "visible_window_limit_reached_rd",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "At least one entry in write queue reaches the visible window limit.",
>> + "ConfigCode": "0x31",
>> + "EventName": "visible_window_limit_reached_wr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A DQS Oscillator MPC command to DRAM.",
>> + "ConfigCode": "0x34",
>> + "EventName": "op_is_dqsosc_mpc",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A DQS Oscillator MRR command to DRAM.",
>> + "ConfigCode": "0x35",
>> + "EventName": "op_is_dqsosc_mrr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A TCR (Temperature Compensated Refresh) MRR command to DRAM.",
>> + "ConfigCode": "0x36",
>> + "EventName": "op_is_tcr_mrr",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A ZQCal Start command to DRAM.",
>> + "ConfigCode": "0x37",
>> + "EventName": "op_is_zqstart",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A ZQCal Latch command to DRAM.",
>> + "ConfigCode": "0x38",
>> + "EventName": "op_is_zqlatch",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A packet at CHI TXREQ interface (request).",
>> + "ConfigCode": "0x39",
>> + "EventName": "chi_txreq",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A packet at CHI TXDAT interface (read data).",
>> + "ConfigCode": "0x3A",
>> + "EventName": "chi_txdat",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A packet at CHI RXDAT interface (write data).",
>> + "ConfigCode": "0x3B",
>> + "EventName": "chi_rxdat",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A packet at CHI RXRSP interface.",
>> + "ConfigCode": "0x3C",
>> + "EventName": "chi_rxrsp",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "A violation detected in TZC.",
>> + "ConfigCode": "0x3D",
>> + "EventName": "tsz_vio",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + },
>> + {
>> + "BriefDescription": "The ddr cycle.",
>> + "ConfigCode": "0x80",
>> + "EventName": "cycle",
>> + "Unit": "ali_drw",
>> + "Compat": "ali_drw_pmu"
>> + }
>> +]
>> diff --git a/tools/perf/pmu-events/jevents.py b/tools/perf/pmu-events/jevents.py
>> index 7cff2c6..aff4051 100755
>> --- a/tools/perf/pmu-events/jevents.py
>> +++ b/tools/perf/pmu-events/jevents.py
>> @@ -257,6 +257,7 @@ class JsonEvent:
>> 'cpu_core': 'cpu_core',
>> 'cpu_atom': 'cpu_atom',
>> 'arm_cmn': 'arm_cmn',
>> + 'ali_drw': 'ali_drw',
>> }
>> return table[unit] if unit in table else f'uncore_{unit.lower()}'
>>
>
> Otherwise, LGTM.
>
> Reviewed-by: Shuai Xue <xueshuai@linux.alibaba.com>
>
> Best Regards,
> Shuai
Thanks!
next prev parent reply other threads:[~2023-05-08 11:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 9:44 [PATCH v2 0/5] Add JSON metrics for arm CMN and Yitian710 DDR Jing Zhang
2023-04-24 9:44 ` [PATCH v2 1/5] driver/perf: Add identifier sysfs file for CMN Jing Zhang
2023-05-01 12:38 ` John Garry
2023-05-04 9:47 ` Robin Murphy
2023-05-04 11:02 ` John Garry
2023-05-04 12:15 ` Robin Murphy
2023-05-05 12:24 ` John Garry
2023-05-08 9:14 ` Jing Zhang
2023-04-24 9:44 ` [PATCH v2 2/5] perf vendor events: Add JSON metrics for CMN-700 Jing Zhang
2023-05-01 12:27 ` John Garry
2023-05-08 11:16 ` Jing Zhang
2023-04-24 9:44 ` [PATCH v2 3/5] driver/perf: Add identifier sysfs file for Yitian 710 DDR Jing Zhang
2023-05-01 12:31 ` John Garry
2023-05-08 11:35 ` Jing Zhang
2023-05-04 7:21 ` Shuai Xue
2023-04-24 9:44 ` [PATCH v2 4/5] perf jevents: Add support for Yitian 710 DDR PMU aliasing Jing Zhang
2023-05-01 12:29 ` John Garry
2023-05-04 7:18 ` Shuai Xue
2023-05-08 11:39 ` Jing Zhang [this message]
2023-04-24 9:44 ` [PATCH v2 5/5] perf vendor events: Add JSON metrics for Yitian 710 DDR Jing Zhang
2023-05-01 12:28 ` John Garry
2023-05-04 7:31 ` Shuai Xue
2023-05-08 11:40 ` Jing Zhang
2023-04-29 21:01 ` [PATCH v2 0/5] Add JSON metrics for arm CMN and Yitian710 DDR Ian Rogers
2023-05-08 11:19 ` Jing Zhang
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=9f01bb3c-2f90-0784-d1ee-ff2ebcd92b1b@linux.alibaba.com \
--to=renyu.zj@linux.alibaba.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ilkka@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.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 \
--cc=xueshuai@linux.alibaba.com \
--cc=zhuo.song@linux.alibaba.com \
/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