linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joakim Zhang <qiangqing.zhang@nxp.com>
To: john.garry@huawei.com, acme@kernel.org, jolsa@redhat.com
Cc: will@kernel.org, linux-perf-users@vger.kernel.org,
	linux-imx@nxp.com, mark.rutland@arm.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH V1 1/4] perf vendor events: Add bandwidth metric for imx8mm
Date: Tue, 19 Jan 2021 10:56:44 +0800	[thread overview]
Message-ID: <20210119025647.12569-2-qiangqing.zhang@nxp.com> (raw)
In-Reply-To: <20210119025647.12569-1-qiangqing.zhang@nxp.com>

Add bandwidth metric for imx8mm.

Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
---
 .../arm64/freescale/imx8mm/sys/metrics.json   | 20 +++++++++++++++++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/tools/perf/pmu-events/arch/arm64/freescale/imx8mm/sys/metrics.json b/tools/perf/pmu-events/arch/arm64/freescale/imx8mm/sys/metrics.json
index 8e553b67cae6..615be286ecaf 100644
--- a/tools/perf/pmu-events/arch/arm64/freescale/imx8mm/sys/metrics.json
+++ b/tools/perf/pmu-events/arch/arm64/freescale/imx8mm/sys/metrics.json
@@ -1,4 +1,20 @@
 [
+   {
+	    "BriefDescription": "bandwidth usage for lpddr4 evk board",
+	    "MetricName": "imx8mm_bandwidth_usage.lpddr4",
+	    "MetricExpr": "(( imx8_ddr0@read\\-cycles@ + imx8_ddr0@write\\-cycles@ ) * 4 * 4 / duration_time) / (750 * 1000000 * 4 * 4)",
+	    "ScaleUnit": "1e2%",
+	    "Unit": "imx8_ddr",
+	    "Compat": "i.MX8MM"
+   },
+   {
+	    "BriefDescription": "bandwidth usage for ddr4 evk board",
+	    "MetricName": "imx8mm_bandwidth_usage.ddr4",
+	    "MetricExpr": "(( imx8_ddr0@read\\-cycles@ + imx8_ddr0@write\\-cycles@ ) * 4 * 4 / duration_time) / (600 * 1000000 * 4 * 4)",
+	    "ScaleUnit": "1e2%",
+	    "Unit": "imx8_ddr",
+	    "Compat": "i.MX8MM"
+   },
    {
 	    "BriefDescription": "bytes all masters read from ddr based on read-cycles event",
 	    "MetricName": "imx8mm_ddr_read.all",
@@ -6,7 +22,7 @@
 	    "ScaleUnit": "9.765625e-4KB",
 	    "Unit": "imx8_ddr",
 	    "Compat": "i.MX8MM"
-    },
+   },
    {
 	    "BriefDescription": "bytes all masters write to ddr based on write-cycles event",
 	    "MetricName": "imx8mm_ddr_write.all",
@@ -14,5 +30,5 @@
 	    "ScaleUnit": "9.765625e-4KB",
 	    "Unit": "imx8_ddr",
 	    "Compat": "i.MX8MM"
-    }
+   }
 ]
-- 
2.17.1


  reply	other threads:[~2021-01-19  2:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  2:56 [PATCH V1 0/4] tools: perf: Add JSON metrics for i.MX8M platforms Joakim Zhang
2021-01-19  2:56 ` Joakim Zhang [this message]
2021-01-19  2:56 ` [PATCH V1 2/4] perf vendor events: Add JSON metrics for imx8mn DDR Perf Joakim Zhang
2021-01-19  2:56 ` [PATCH V1 3/4] perf vendor events: Add JSON metrics for imx8mq " Joakim Zhang
2021-01-19 10:40   ` John Garry
2021-01-19 11:00     ` Joakim Zhang
2021-01-19 12:27       ` John Garry
2021-01-20  5:46         ` Joakim Zhang
2021-01-20  9:25           ` John Garry
2021-01-21 10:24             ` Joakim Zhang
2021-01-19  2:56 ` [PATCH V1 4/4] perf vendor events: Add JSON metrics for imx8mp " Joakim 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=20210119025647.12569-2-qiangqing.zhang@nxp.com \
    --to=qiangqing.zhang@nxp.com \
    --cc=acme@kernel.org \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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).