linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
	<alexander.shishkin@linux.intel.com>, <jolsa@redhat.com>,
	<namhyung@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
	<will@kernel.org>, <mark.rutland@arm.com>,
	<zhangshaokun@hisilicon.com>, John Garry <john.garry@huawei.com>
Subject: [PATCH 1/4] perf jevents: Fix Hisi hip08 DDRC PMU eventname
Date: Wed, 4 Sep 2019 23:54:41 +0800	[thread overview]
Message-ID: <1567612484-195727-2-git-send-email-john.garry@huawei.com> (raw)
In-Reply-To: <1567612484-195727-1-git-send-email-john.garry@huawei.com>

The "EventName" for the DDRC precharge command event is incorrect, so fix
it.

Fixes: 57cc732479ba ("perf jevents: Add support for Hisi hip08 DDRC PMU aliasing")
Signed-off-by: John Garry <john.garry@huawei.com>
---
 .../perf/pmu-events/arch/arm64/hisilicon/hip08/uncore-ddrc.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/uncore-ddrc.json b/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/uncore-ddrc.json
index 0d1556fcdffe..99f4fc425564 100644
--- a/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/uncore-ddrc.json
+++ b/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/uncore-ddrc.json
@@ -15,7 +15,7 @@
    },
    {
 	    "EventCode": "0x04",
-	    "EventName": "uncore_hisi_ddrc.flux_wr",
+	    "EventName": "uncore_hisi_ddrc.pre_cmd",
 	    "BriefDescription": "DDRC precharge commands",
 	    "PublicDescription": "DDRC precharge commands",
 	    "Unit": "hisi_sccl,ddrc",
-- 
2.17.1


  reply	other threads:[~2019-09-04 15:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 15:54 [PATCH 0/4] HiSilicon hip08 uncore PMU events additions John Garry
2019-09-04 15:54 ` John Garry [this message]
2019-10-21 23:19   ` [tip: perf/core] perf vendor events arm64: Fix Hisi hip08 DDRC PMU eventname tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 2/4] perf jevents: Add some missing events for Hisi hip08 DDRC PMU John Garry
2019-10-21 23:19   ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 3/4] perf jevents: Add some missing events for Hisi hip08 L3C PMU John Garry
2019-10-21 23:19   ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 4/4] perf jevents: Add some missing events for Hisi hip08 HHA PMU John Garry
2019-10-21 23:19   ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-10-04 14:30 ` [PATCH 0/4] HiSilicon hip08 uncore PMU events additions John Garry
2019-10-04 14:36   ` Arnaldo Carvalho de Melo
2019-10-04 14:38     ` Arnaldo Carvalho de Melo
2019-10-04 14:59       ` Will Deacon
2019-10-04 14:59       ` John Garry
2019-10-04 15:18         ` Arnaldo Carvalho de Melo
2019-10-04 16:30           ` John Garry
2019-10-04 19:06             ` Arnaldo Carvalho de Melo
2019-10-07 13:40               ` John Garry
2019-10-09  1:14 ` Shaokun Zhang
2019-10-15 15:16   ` Arnaldo Carvalho de Melo

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=1567612484-195727-2-git-send-email-john.garry@huawei.com \
    --to=john.garry@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --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 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).