From: Disha Goel <disgoel@linux.ibm.com>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
acme@kernel.org, jolsa@kernel.org, adrian.hunter@intel.com,
irogers@google.com, james.clark@arm.com, namhyung@kernel.org
Cc: linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.ibm.com, kjain@linux.ibm.com,
disgoel@linux.vnet.ibm.com
Subject: Re: [PATCH] perf vendor events: Update datasource event name to fix duplicate events
Date: Mon, 27 Nov 2023 17:32:00 +0530 [thread overview]
Message-ID: <92bbba90-c7e4-43de-98dc-497ca323eacc@linux.ibm.com> (raw)
In-Reply-To: <20231123160110.94090-1-atrajeev@linux.vnet.ibm.com>
On 23/11/23 9:31 pm, Athira Rajeev wrote:
> Running "perf list" on powerpc fails with segfault
> as below:
>
> ./perf list
> Segmentation fault (core dumped)
>
> This happens because of duplicate events in the json list.
> The powerpc Json event list contains some event with same
> event name, but different event code. They are:
> - PM_INST_FROM_L3MISS (Present in datasource and frontend)
> - PM_MRK_DATA_FROM_L2MISS (Present in datasource and marked)
> - PM_MRK_INST_FROM_L3MISS (Present in datasource and marked)
> - PM_MRK_DATA_FROM_L3MISS (Present in datasource and marked)
>
> pmu_events_table__num_events uses the value from
> table_pmu->num_entries which includes duplicate events as
> well. This causes issue during "perf list" and results in
> segmentation fault.
>
> Since both event codes are valid, append _DSRC to the Data
> Source events (datasource.json), so that they would have a
> unique name. Also add PM_DATA_FROM_L2MISS_DSRC and
> PM_DATA_FROM_L3MISS_DSRC events. With the fix, perf list
> works as expected.
>
> Fixes: fc1435807533 ("perf vendor events power10: Update JSON/events")
> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
I have tested the patch on Power10 machine. Perf list works correctly without any segfault now.
# ./perf list
List of pre-defined events (to be used in -e or -M):
branch-instructions OR branches [Hardware event]
branch-misses [Hardware event]
Tested-by: Disha Goel <disgoel@linux.ibm.com>
> ---
> .../arch/powerpc/power10/datasource.json | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/pmu-events/arch/powerpc/power10/datasource.json b/tools/perf/pmu-events/arch/powerpc/power10/datasource.json
> index 6b0356f2d301..0eeaaf1a95b8 100644
> --- a/tools/perf/pmu-events/arch/powerpc/power10/datasource.json
> +++ b/tools/perf/pmu-events/arch/powerpc/power10/datasource.json
> @@ -99,6 +99,11 @@
> "EventName": "PM_INST_FROM_L2MISS",
> "BriefDescription": "The processor's instruction cache was reloaded from a source beyond the local core's L2 due to a demand miss."
> },
> + {
> + "EventCode": "0x0003C0000000C040",
> + "EventName": "PM_DATA_FROM_L2MISS_DSRC",
> + "BriefDescription": "The processor's L1 data cache was reloaded from a source beyond the local core's L2 due to a demand miss."
> + },
> {
> "EventCode": "0x000380000010C040",
> "EventName": "PM_INST_FROM_L2MISS_ALL",
> @@ -161,9 +166,14 @@
> },
> {
> "EventCode": "0x000780000000C040",
> - "EventName": "PM_INST_FROM_L3MISS",
> + "EventName": "PM_INST_FROM_L3MISS_DSRC",
> "BriefDescription": "The processor's instruction cache was reloaded from beyond the local core's L3 due to a demand miss."
> },
> + {
> + "EventCode": "0x0007C0000000C040",
> + "EventName": "PM_DATA_FROM_L3MISS_DSRC",
> + "BriefDescription": "The processor's L1 data cache was reloaded from beyond the local core's L3 due to a demand miss."
> + },
> {
> "EventCode": "0x000780000010C040",
> "EventName": "PM_INST_FROM_L3MISS_ALL",
> @@ -981,7 +991,7 @@
> },
> {
> "EventCode": "0x0003C0000000C142",
> - "EventName": "PM_MRK_DATA_FROM_L2MISS",
> + "EventName": "PM_MRK_DATA_FROM_L2MISS_DSRC",
> "BriefDescription": "The processor's L1 data cache was reloaded from a source beyond the local core's L2 due to a demand miss for a marked instruction."
> },
> {
> @@ -1046,12 +1056,12 @@
> },
> {
> "EventCode": "0x000780000000C142",
> - "EventName": "PM_MRK_INST_FROM_L3MISS",
> + "EventName": "PM_MRK_INST_FROM_L3MISS_DSRC",
> "BriefDescription": "The processor's instruction cache was reloaded from beyond the local core's L3 due to a demand miss for a marked instruction."
> },
> {
> "EventCode": "0x0007C0000000C142",
> - "EventName": "PM_MRK_DATA_FROM_L3MISS",
> + "EventName": "PM_MRK_DATA_FROM_L3MISS_DSRC",
> "BriefDescription": "The processor's L1 data cache was reloaded from beyond the local core's L3 due to a demand miss for a marked instruction."
> },
> {
next prev parent reply other threads:[~2023-11-27 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 16:01 [PATCH] perf vendor events: Update datasource event name to fix duplicate events Athira Rajeev
2023-11-27 12:02 ` Disha Goel [this message]
2023-11-29 5:21 ` Athira Rajeev
2023-12-03 15:57 ` Athira Rajeev
2023-12-04 20:00 ` Arnaldo Carvalho de Melo
2023-12-04 20:12 ` Ian Rogers
2023-12-04 20:20 ` Arnaldo Carvalho de Melo
2023-12-04 20:22 ` Arnaldo Carvalho de Melo
2023-12-04 21:13 ` Ian Rogers
2023-12-05 7:16 ` Athira Rajeev
2023-12-05 7:14 ` Athira Rajeev
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=92bbba90-c7e4-43de-98dc-497ca323eacc@linux.ibm.com \
--to=disgoel@linux.ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=namhyung@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).