From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
John Garry <john.g.garry@oracle.com>,
Will Deacon <will@kernel.org>,
James Clark <james.clark@linaro.org>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linux.dev>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Samuel Holland <samuel.holland@sifive.com>,
Charles Ci-Jyun Wu <dminus@andestech.com>,
Locus Wei-Han Chen <locus84@andestech.com>,
Atish Patra <atishp@rivosinc.com>,
Ji Sheng Teoh <jisheng.teoh@starfivetech.com>,
Inochi Amaoto <inochiama@outlook.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Xu Yang <xu.yang_2@nxp.com>, Sandipan Das <sandipan.das@amd.com>,
Guilherme Amadio <amadio@gentoo.org>,
Changbin Du <changbin.du@huawei.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, vincent.chen@sifive.com,
greentime.hu@sifive.com, Eric Lin <eric.lin@sifive.com>
Subject: [PATCH v1 4/5] perf pmu-events: Remove duplicated riscv firmware event
Date: Mon, 5 Aug 2024 12:44:23 -0700 [thread overview]
Message-ID: <20240805194424.597244-4-irogers@google.com> (raw)
In-Reply-To: <20240805194424.597244-1-irogers@google.com>
FW_SFENCE_VMA_RECEIVED is repeated twice in the file which will break
invariants in perf list as discussed in this thread:
https://lore.kernel.org/linux-perf-users/20240719081651.24853-1-eric.lin@sifive.com/
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/pmu-events/arch/riscv/andes/ax45/firmware.json | 3 ---
tools/perf/pmu-events/arch/riscv/sifive/u74/firmware.json | 3 ---
.../perf/pmu-events/arch/riscv/starfive/dubhe-80/firmware.json | 3 ---
.../perf/pmu-events/arch/riscv/thead/c900-legacy/firmware.json | 3 ---
4 files changed, 12 deletions(-)
diff --git a/tools/perf/pmu-events/arch/riscv/andes/ax45/firmware.json b/tools/perf/pmu-events/arch/riscv/andes/ax45/firmware.json
index 9b4a032186a7..5a996fa4b837 100644
--- a/tools/perf/pmu-events/arch/riscv/andes/ax45/firmware.json
+++ b/tools/perf/pmu-events/arch/riscv/andes/ax45/firmware.json
@@ -35,9 +35,6 @@
{
"ArchStdEvent": "FW_SFENCE_VMA_RECEIVED"
},
- {
- "ArchStdEvent": "FW_SFENCE_VMA_RECEIVED"
- },
{
"ArchStdEvent": "FW_SFENCE_VMA_ASID_RECEIVED"
},
diff --git a/tools/perf/pmu-events/arch/riscv/sifive/u74/firmware.json b/tools/perf/pmu-events/arch/riscv/sifive/u74/firmware.json
index 9b4a032186a7..5a996fa4b837 100644
--- a/tools/perf/pmu-events/arch/riscv/sifive/u74/firmware.json
+++ b/tools/perf/pmu-events/arch/riscv/sifive/u74/firmware.json
@@ -35,9 +35,6 @@
{
"ArchStdEvent": "FW_SFENCE_VMA_RECEIVED"
},
- {
- "ArchStdEvent": "FW_SFENCE_VMA_RECEIVED"
- },
{
"ArchStdEvent": "FW_SFENCE_VMA_ASID_RECEIVED"
},
diff --git a/tools/perf/pmu-events/arch/riscv/starfive/dubhe-80/firmware.json b/tools/perf/pmu-events/arch/riscv/starfive/dubhe-80/firmware.json
index 9b4a032186a7..5a996fa4b837 100644
--- a/tools/perf/pmu-events/arch/riscv/starfive/dubhe-80/firmware.json
+++ b/tools/perf/pmu-events/arch/riscv/starfive/dubhe-80/firmware.json
@@ -35,9 +35,6 @@
{
"ArchStdEvent": "FW_SFENCE_VMA_RECEIVED"
},
- {
- "ArchStdEvent": "FW_SFENCE_VMA_RECEIVED"
- },
{
"ArchStdEvent": "FW_SFENCE_VMA_ASID_RECEIVED"
},
diff --git a/tools/perf/pmu-events/arch/riscv/thead/c900-legacy/firmware.json b/tools/perf/pmu-events/arch/riscv/thead/c900-legacy/firmware.json
index 9b4a032186a7..5a996fa4b837 100644
--- a/tools/perf/pmu-events/arch/riscv/thead/c900-legacy/firmware.json
+++ b/tools/perf/pmu-events/arch/riscv/thead/c900-legacy/firmware.json
@@ -35,9 +35,6 @@
{
"ArchStdEvent": "FW_SFENCE_VMA_RECEIVED"
},
- {
- "ArchStdEvent": "FW_SFENCE_VMA_RECEIVED"
- },
{
"ArchStdEvent": "FW_SFENCE_VMA_ASID_RECEIVED"
},
--
2.46.0.rc2.264.g509ed76dc8-goog
next prev parent reply other threads:[~2024-08-05 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 19:44 [PATCH v1 1/5] perf test: Add build test for JEVENTS_ARCH=all Ian Rogers
2024-08-05 19:44 ` [PATCH v1 2/5] perf pmu-events: Change dependencies for empty-pmu-events.c test Ian Rogers
2024-08-05 20:03 ` Arnaldo Carvalho de Melo
2024-08-05 19:44 ` [PATCH v1 3/5] perf pmu-events: Remove duplicated ampereone event Ian Rogers
2024-08-05 19:44 ` Ian Rogers [this message]
2024-08-06 3:54 ` [PATCH v1 4/5] perf pmu-events: Remove duplicated riscv firmware event Eric Lin
2024-08-06 4:05 ` Ian Rogers
2024-08-06 13:38 ` Arnaldo Carvalho de Melo
2024-08-06 13:50 ` Arnaldo Carvalho de Melo
2024-08-06 13:51 ` Arnaldo Carvalho de Melo
2024-08-06 15:50 ` Eric Lin
2024-08-06 17:04 ` Arnaldo Carvalho de Melo
2024-08-05 19:44 ` [PATCH v1 5/5] perf jevents.py: Ensure event names aren't duplicated Ian Rogers
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=20240805194424.597244-4-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=amadio@gentoo.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=changbin.du@huawei.com \
--cc=dminus@andestech.com \
--cc=eric.lin@sifive.com \
--cc=greentime.hu@sifive.com \
--cc=inochiama@outlook.com \
--cc=james.clark@linaro.org \
--cc=jisheng.teoh@starfivetech.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=locus84@andestech.com \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=samuel.holland@sifive.com \
--cc=sandipan.das@amd.com \
--cc=vincent.chen@sifive.com \
--cc=will@kernel.org \
--cc=xu.yang_2@nxp.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).