All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
To: john.garry@huawei.com, will@kernel.org,
	mathieu.poirier@linaro.org, leo.yan@linaro.org,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com, namhyung@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v8 3/3] perf vendor events arm64: Add "_" to the event name, which starts with a number
Date: Fri,  5 Mar 2021 19:18:41 +0900	[thread overview]
Message-ID: <20210305101841.3133721-4-nakamura.shun@fujitsu.com> (raw)
In-Reply-To: <20210305101841.3133721-1-nakamura.shun@fujitsu.com>

The perf parser does not support event names that start with a number.
This patch adds "_" to the event name, which starts with a number.

Signed-off-by: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
---
 .../pmu-events/arch/arm64/fujitsu/a64fx/other.json     | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json b/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json
index 68b8e46d6140..10c823ac26cc 100644
--- a/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json
+++ b/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json
@@ -98,31 +98,31 @@
   {
     "PublicDescription": "This event counts every cycle that no instruction was committed, but counts at the time when commits MOVPRFX only.",
     "EventCode": "0x190",
-    "EventName": "0INST_COMMIT",
+    "EventName": "_0INST_COMMIT",
     "BriefDescription": "This event counts every cycle that no instruction was committed, but counts at the time when commits MOVPRFX only."
   },
   {
     "PublicDescription": "This event counts every cycle that one instruction is committed.",
     "EventCode": "0x191",
-    "EventName": "1INST_COMMIT",
+    "EventName": "_1INST_COMMIT",
     "BriefDescription": "This event counts every cycle that one instruction is committed."
   },
   {
     "PublicDescription": "This event counts every cycle that two instructions are committed.",
     "EventCode": "0x192",
-    "EventName": "2INST_COMMIT",
+    "EventName": "_2INST_COMMIT",
     "BriefDescription": "This event counts every cycle that two instructions are committed."
   },
   {
     "PublicDescription": "This event counts every cycle that three instructions are committed.",
     "EventCode": "0x193",
-    "EventName": "3INST_COMMIT",
+    "EventName": "_3INST_COMMIT",
     "BriefDescription": "This event counts every cycle that three instructions are committed."
   },
   {
     "PublicDescription": "This event counts every cycle that four instructions are committed.",
     "EventCode": "0x194",
-    "EventName": "4INST_COMMIT",
+    "EventName": "_4INST_COMMIT",
     "BriefDescription": "This event counts every cycle that four instructions are committed."
   },
   {
-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
To: john.garry@huawei.com, will@kernel.org,
	mathieu.poirier@linaro.org, leo.yan@linaro.org,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com, namhyung@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v8 3/3] perf vendor events arm64: Add "_" to the event name, which starts with a number
Date: Fri,  5 Mar 2021 19:18:41 +0900	[thread overview]
Message-ID: <20210305101841.3133721-4-nakamura.shun@fujitsu.com> (raw)
In-Reply-To: <20210305101841.3133721-1-nakamura.shun@fujitsu.com>

The perf parser does not support event names that start with a number.
This patch adds "_" to the event name, which starts with a number.

Signed-off-by: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
---
 .../pmu-events/arch/arm64/fujitsu/a64fx/other.json     | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json b/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json
index 68b8e46d6140..10c823ac26cc 100644
--- a/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json
+++ b/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json
@@ -98,31 +98,31 @@
   {
     "PublicDescription": "This event counts every cycle that no instruction was committed, but counts at the time when commits MOVPRFX only.",
     "EventCode": "0x190",
-    "EventName": "0INST_COMMIT",
+    "EventName": "_0INST_COMMIT",
     "BriefDescription": "This event counts every cycle that no instruction was committed, but counts at the time when commits MOVPRFX only."
   },
   {
     "PublicDescription": "This event counts every cycle that one instruction is committed.",
     "EventCode": "0x191",
-    "EventName": "1INST_COMMIT",
+    "EventName": "_1INST_COMMIT",
     "BriefDescription": "This event counts every cycle that one instruction is committed."
   },
   {
     "PublicDescription": "This event counts every cycle that two instructions are committed.",
     "EventCode": "0x192",
-    "EventName": "2INST_COMMIT",
+    "EventName": "_2INST_COMMIT",
     "BriefDescription": "This event counts every cycle that two instructions are committed."
   },
   {
     "PublicDescription": "This event counts every cycle that three instructions are committed.",
     "EventCode": "0x193",
-    "EventName": "3INST_COMMIT",
+    "EventName": "_3INST_COMMIT",
     "BriefDescription": "This event counts every cycle that three instructions are committed."
   },
   {
     "PublicDescription": "This event counts every cycle that four instructions are committed.",
     "EventCode": "0x194",
-    "EventName": "4INST_COMMIT",
+    "EventName": "_4INST_COMMIT",
     "BriefDescription": "This event counts every cycle that four instructions are committed."
   },
   {
-- 
2.25.1


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

  parent reply	other threads:[~2021-03-05 10:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 10:18 [PATCH v8 0/3] perf vendor events: Support PMU events for A64FX Shunsuke Nakamura
2021-03-05 10:18 ` Shunsuke Nakamura
2021-03-05 10:18 ` [PATCH v8 1/3] perf vendor events arm64: Add more common and uarch events Shunsuke Nakamura
2021-03-05 10:18   ` Shunsuke Nakamura
2021-03-05 10:18 ` [PATCH v8 2/3] perf vendor events arm64: Add Fujitsu A64FX pmu event Shunsuke Nakamura
2021-03-05 10:18   ` Shunsuke Nakamura
2021-03-05 10:18 ` Shunsuke Nakamura [this message]
2021-03-05 10:18   ` [PATCH v8 3/3] perf vendor events arm64: Add "_" to the event name, which starts with a number Shunsuke Nakamura
2021-03-05 11:09   ` John Garry
2021-03-05 11:09     ` John Garry
2021-03-08 10:44     ` nakamura.shun
2021-03-08 10:44       ` nakamura.shun

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=20210305101841.3133721-4-nakamura.shun@fujitsu.com \
    --to=nakamura.shun@fujitsu.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@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 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.