All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Joakim Zhang <qiangqing.zhang@nxp.com>,
	"acme@kernel.org" <acme@kernel.org>,
	"will@kernel.org" <will@kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"jolsa@redhat.com" <jolsa@redhat.com>,
	"irogers@google.com" <irogers@google.com>,
	"leo.yan@linaro.org" <leo.yan@linaro.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"alexander.shishkin@linux.intel.com" 
	<alexander.shishkin@linux.intel.com>,
	"namhyung@kernel.org" <namhyung@kernel.org>,
	"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>
Cc: Linuxarm <linuxarm@huawei.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Zhangshaokun <zhangshaokun@hisilicon.com>,
	"james.clark@arm.com" <james.clark@arm.com>,
	dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH RFC v4 13/13] perf vendor events: Add JSON metrics for imx8mm DDR Perf
Date: Mon, 12 Oct 2020 11:34:40 +0100	[thread overview]
Message-ID: <14cf6eae-f865-bd0d-72c1-57aeb87f2570@huawei.com> (raw)
In-Reply-To: <DB8PR04MB67950A459A08343CA3A779A4E6070@DB8PR04MB6795.eurprd04.prod.outlook.com>

On 12/10/2020 11:03, Joakim Zhang wrote:
>> --- /dev/null
>> +++ b/tools/perf/pmu-events/arch/arm64/freescale/imx8mm/sys/ddrc.json
>> @@ -0,0 +1,39 @@
>> +[
>> +   {
>> +           "BriefDescription": "ddr cycles event",
>> +           "EventCode": "0x00",
>> +           "EventName": "imx8_ddr.cycles",
> Could you help change to imx8mm_ddr.cycles? Thanks a lot!

Can do.

Note that I want to improve perf list in future such that alias 
"imx8_ddr.cycles" removes kernel PMU events which this alias is 
matching. The motivation is that perf list can be swamped by kernel 
uncore PMU events listing.

> 
>> +           "Unit": "imx8_ddr",
>> +           "Compat": "i.MX8MM"


WARNING: multiple messages have this Message-ID (diff)
From: John Garry <john.garry@huawei.com>
To: Joakim Zhang <qiangqing.zhang@nxp.com>,
	"acme@kernel.org" <acme@kernel.org>,
	"will@kernel.org" <will@kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"jolsa@redhat.com" <jolsa@redhat.com>,
	"irogers@google.com" <irogers@google.com>,
	"leo.yan@linaro.org" <leo.yan@linaro.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"alexander.shishkin@linux.intel.com"
	<alexander.shishkin@linux.intel.com>,
	"namhyung@kernel.org" <namhyung@kernel.org>,
	"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>
Cc: Linuxarm <linuxarm@huawei.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Zhangshaokun <zhangshaokun@hisilicon.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"james.clark@arm.com" <james.clark@arm.com>
Subject: Re: [PATCH RFC v4 13/13] perf vendor events: Add JSON metrics for imx8mm DDR Perf
Date: Mon, 12 Oct 2020 11:34:40 +0100	[thread overview]
Message-ID: <14cf6eae-f865-bd0d-72c1-57aeb87f2570@huawei.com> (raw)
In-Reply-To: <DB8PR04MB67950A459A08343CA3A779A4E6070@DB8PR04MB6795.eurprd04.prod.outlook.com>

On 12/10/2020 11:03, Joakim Zhang wrote:
>> --- /dev/null
>> +++ b/tools/perf/pmu-events/arch/arm64/freescale/imx8mm/sys/ddrc.json
>> @@ -0,0 +1,39 @@
>> +[
>> +   {
>> +           "BriefDescription": "ddr cycles event",
>> +           "EventCode": "0x00",
>> +           "EventName": "imx8_ddr.cycles",
> Could you help change to imx8mm_ddr.cycles? Thanks a lot!

Can do.

Note that I want to improve perf list in future such that alias 
"imx8_ddr.cycles" removes kernel PMU events which this alias is 
matching. The motivation is that perf list can be swamped by kernel 
uncore PMU events listing.

> 
>> +           "Unit": "imx8_ddr",
>> +           "Compat": "i.MX8MM"


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-12 10:37 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 10:15 [PATCH RFC v4 00/13] perf pmu-events: Support event aliasing for system PMUs John Garry
2020-10-08 10:15 ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 01/13] perf jevents: Add support for an extra directory level John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 02/13] perf jevents: Add support for system events tables John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 03/13] perf pmu: Add pmu_id() John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 04/13] perf pmu: Add pmu_add_sys_aliases() John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 05/13] perf vendor events arm64: Add Architected events smmuv3-pmcg.json John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 06/13] perf vendor events arm64: Add hip09 SMMUv3 PMCG events John Garry
2020-10-08 10:15   ` John Garry
2020-10-14 18:06   ` Robin Murphy
2020-10-14 18:06     ` Robin Murphy
2020-10-15  7:47     ` John Garry
2020-10-15  7:47       ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 07/13] perf vendor events arm64: Add hip09 uncore events John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 08/13] perf metricgroup: Fix uncore metric expressions John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 09/13] perf metricgroup: Hack a fix for aliases when covering multiple PMUs John Garry
2020-10-08 10:15   ` John Garry
2020-10-18  8:50   ` [perf metricgroup] fcc9c5243c: perf-sanity-tests.Parse_and_process_metrics.fail kernel test robot
2020-10-18 23:30     ` Ian Rogers
2020-10-18 23:30       ` Ian Rogers
2020-10-19  1:52       ` Andi Kleen
2020-10-19  1:52         ` Andi Kleen
2020-10-19  8:02         ` Jin, Yao
2020-10-19  8:02           ` Jin, Yao
2020-10-19  9:48       ` John Garry
2020-10-19  9:48         ` John Garry
2020-10-19 11:49         ` Jin, Yao
2020-10-19 11:49           ` Jin, Yao
2020-10-19 16:20         ` Ian Rogers
2020-10-19 16:20           ` Ian Rogers
2020-10-19 17:04           ` John Garry
2020-10-19 17:04             ` John Garry
2020-10-20  8:56           ` kajoljain
2020-10-20  8:56             ` kajoljain
2020-10-20 16:53             ` Ian Rogers
2020-10-20 16:53               ` Ian Rogers
2020-11-03 14:43               ` John Garry
2020-11-03 14:43                 ` John Garry
2020-11-03 16:05                 ` Ian Rogers
2020-11-03 16:05                   ` Ian Rogers
2020-11-03 16:54                   ` John Garry
2020-11-03 16:54                     ` John Garry
2020-11-04  4:58                     ` kajoljain
2020-11-04  4:58                       ` kajoljain
2020-10-08 10:15 ` [PATCH RFC v4 10/13] perf metricgroup: Split up metricgroup__print() John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 11/13] perf metricgroup: Support printing metric groups for system PMUs John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 12/13] perf metricgroup: Support adding metrics " John Garry
2020-10-08 10:15   ` John Garry
2020-10-08 10:15 ` [PATCH RFC v4 13/13] perf vendor events: Add JSON metrics for imx8mm DDR Perf John Garry
2020-10-08 10:15   ` John Garry
2020-10-12 10:03   ` Joakim Zhang
2020-10-12 10:03     ` Joakim Zhang
2020-10-12 10:34     ` John Garry [this message]
2020-10-12 10:34       ` John Garry
2020-10-08 11:27 ` [PATCH RFC v4 00/13] perf pmu-events: Support event aliasing for system PMUs kajoljain
2020-10-08 11:27   ` kajoljain
2020-10-08 11:49   ` John Garry
2020-10-08 11:49     ` John Garry
2020-10-14 11:16     ` Jiri Olsa
2020-10-14 11:16       ` Jiri Olsa
2020-10-14 17:41       ` John Garry
2020-10-14 17:41         ` John Garry

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=14cf6eae-f865-bd0d-72c1-57aeb87f2570@huawei.com \
    --to=john.garry@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@redhat.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=qiangqing.zhang@nxp.com \
    --cc=will@kernel.org \
    --cc=zhangshaokun@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.