From: "Liang, Kan" <kan.liang@linux.intel.com>
To: kajoljain <kjain@linux.ibm.com>,
acme@kernel.org, irogers@google.com, peterz@infradead.org,
mingo@redhat.com, namhyung@kernel.org, jolsa@kernel.org,
adrian.hunter@intel.com, john.g.garry@oracle.com,
will@kernel.org, james.clark@arm.com, mike.leach@linaro.org,
leo.yan@linaro.org, yuhaixin.yhx@linux.alibaba.com,
renyu.zj@linux.alibaba.com, tmricht@linux.ibm.com,
ravi.bangoria@amd.com, atrajeev@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 0/7] Clean up perf mem
Date: Tue, 16 Jan 2024 11:37:02 -0500 [thread overview]
Message-ID: <a0540796-1933-4057-8282-aa219ddda4fe@linux.intel.com> (raw)
In-Reply-To: <cd7dc93f-ade9-6403-a732-2daca8e6cff9@linux.ibm.com>
On 2024-01-16 9:05 a.m., kajoljain wrote:
>> For powerpc, the patch 3 introduced a perf_mem_events_power, which
>> doesn't have ldlat. But it only be assigned to the pmu->is_core. I'm not
>> sure if it's the problem.
> Hi Kan,
> Correct there were some small issues with patch 3, I added fix for that.
>
Thanks Kajol Jain! I will fold your fix into V4.
>> Also, S390 still uses the default perf_mem_events, which includes ldlat.
>> I'm not sure if S390 supports the ldlat.
> I checked it, I didn't find ldlat parameter defined in arch/s390
> directory. I think its better to make default ldlat value as false
> in tools/perf/util/mem-events.c file.
The s390 may not be the only user for the default perf_mem_events[] in
the tools/perf/util/mem-events.c. We probably cannot change the default
value.
We may share the perf_mem_events_power[] between powerpc and s390. (We
did the similar share for arm and arm64.)
How about the below patch (not tested.)
diff --git a/tools/perf/arch/s390/util/pmu.c
b/tools/perf/arch/s390/util/pmu.c
index 225d7dc2379c..411034c984bb 100644
--- a/tools/perf/arch/s390/util/pmu.c
+++ b/tools/perf/arch/s390/util/pmu.c
@@ -8,6 +8,7 @@
#include <string.h>
#include "../../../util/pmu.h"
+#include "../../powerpc/util/mem-events.h"
#define S390_PMUPAI_CRYPTO "pai_crypto"
#define S390_PMUPAI_EXT "pai_ext"
@@ -21,5 +22,5 @@ void perf_pmu__arch_init(struct perf_pmu *pmu)
pmu->selectable = true;
if (pmu->is_core)
- pmu->mem_events = perf_mem_events;
+ pmu->mem_events = perf_mem_events_power;
}
However, the original s390 code doesn't include any s390 specific code
for perf_mem. So I thought it uses the default perf_mem_events[].
Is there something I missed?
Or does the s390 even support mem events? If not, I may remove the
mem_events from s390.
Thanks,
Kan
WARNING: multiple messages have this Message-ID (diff)
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: kajoljain <kjain@linux.ibm.com>,
acme@kernel.org, irogers@google.com, peterz@infradead.org,
mingo@redhat.com, namhyung@kernel.org, jolsa@kernel.org,
adrian.hunter@intel.com, john.g.garry@oracle.com,
will@kernel.org, james.clark@arm.com, mike.leach@linaro.org,
leo.yan@linaro.org, yuhaixin.yhx@linux.alibaba.com,
renyu.zj@linux.alibaba.com, tmricht@linux.ibm.com,
ravi.bangoria@amd.com, atrajeev@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 0/7] Clean up perf mem
Date: Tue, 16 Jan 2024 11:37:02 -0500 [thread overview]
Message-ID: <a0540796-1933-4057-8282-aa219ddda4fe@linux.intel.com> (raw)
In-Reply-To: <cd7dc93f-ade9-6403-a732-2daca8e6cff9@linux.ibm.com>
On 2024-01-16 9:05 a.m., kajoljain wrote:
>> For powerpc, the patch 3 introduced a perf_mem_events_power, which
>> doesn't have ldlat. But it only be assigned to the pmu->is_core. I'm not
>> sure if it's the problem.
> Hi Kan,
> Correct there were some small issues with patch 3, I added fix for that.
>
Thanks Kajol Jain! I will fold your fix into V4.
>> Also, S390 still uses the default perf_mem_events, which includes ldlat.
>> I'm not sure if S390 supports the ldlat.
> I checked it, I didn't find ldlat parameter defined in arch/s390
> directory. I think its better to make default ldlat value as false
> in tools/perf/util/mem-events.c file.
The s390 may not be the only user for the default perf_mem_events[] in
the tools/perf/util/mem-events.c. We probably cannot change the default
value.
We may share the perf_mem_events_power[] between powerpc and s390. (We
did the similar share for arm and arm64.)
How about the below patch (not tested.)
diff --git a/tools/perf/arch/s390/util/pmu.c
b/tools/perf/arch/s390/util/pmu.c
index 225d7dc2379c..411034c984bb 100644
--- a/tools/perf/arch/s390/util/pmu.c
+++ b/tools/perf/arch/s390/util/pmu.c
@@ -8,6 +8,7 @@
#include <string.h>
#include "../../../util/pmu.h"
+#include "../../powerpc/util/mem-events.h"
#define S390_PMUPAI_CRYPTO "pai_crypto"
#define S390_PMUPAI_EXT "pai_ext"
@@ -21,5 +22,5 @@ void perf_pmu__arch_init(struct perf_pmu *pmu)
pmu->selectable = true;
if (pmu->is_core)
- pmu->mem_events = perf_mem_events;
+ pmu->mem_events = perf_mem_events_power;
}
However, the original s390 code doesn't include any s390 specific code
for perf_mem. So I thought it uses the default perf_mem_events[].
Is there something I missed?
Or does the s390 even support mem events? If not, I may remove the
mem_events from s390.
Thanks,
Kan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-16 16:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 19:51 [PATCH V3 0/7] Clean up perf mem kan.liang
2023-12-13 19:51 ` kan.liang
2023-12-13 19:51 ` [PATCH V3 1/7] perf mem: Add mem_events into the supported perf_pmu kan.liang
2023-12-13 19:51 ` kan.liang
2023-12-19 8:48 ` kajoljain
2023-12-19 8:48 ` kajoljain
2023-12-13 19:51 ` [PATCH V3 2/7] perf mem: Clean up perf_mem_events__ptr() kan.liang
2023-12-13 19:51 ` kan.liang
2024-01-16 13:22 ` kajoljain
2024-01-16 13:22 ` kajoljain
2023-12-13 19:51 ` [PATCH V3 3/7] perf mem: Clean up perf_mem_events__name() kan.liang
2023-12-13 19:51 ` kan.liang
2024-01-16 13:58 ` kajoljain
2024-01-16 13:58 ` kajoljain
2023-12-13 19:51 ` [PATCH V3 4/7] perf mem: Clean up perf_mem_event__supported() kan.liang
2023-12-13 19:51 ` kan.liang
2023-12-13 19:51 ` [PATCH V3 5/7] perf mem: Clean up is_mem_loads_aux_event() kan.liang
2023-12-13 19:51 ` kan.liang
2023-12-13 19:51 ` [PATCH V3 6/7] perf mem: Clean up perf_mem_events__record_args() kan.liang
2023-12-13 19:51 ` kan.liang
2023-12-13 19:51 ` [PATCH V3 7/7] perf mem: Clean up perf_pmus__num_mem_pmus() kan.liang
2023-12-13 19:51 ` kan.liang
2023-12-16 3:29 ` [PATCH V3 0/7] Clean up perf mem Leo Yan
2023-12-16 3:29 ` Leo Yan
2023-12-19 9:26 ` kajoljain
2023-12-19 9:26 ` kajoljain
2023-12-19 14:15 ` Liang, Kan
2023-12-19 14:15 ` Liang, Kan
2024-01-02 20:08 ` Liang, Kan
2024-01-02 20:08 ` Liang, Kan
2024-01-05 6:38 ` kajoljain
2024-01-05 6:38 ` kajoljain
2024-01-05 14:38 ` Liang, Kan
2024-01-05 14:38 ` Liang, Kan
2024-01-16 14:05 ` kajoljain
2024-01-16 14:05 ` kajoljain
2024-01-16 16:37 ` Liang, Kan [this message]
2024-01-16 16:37 ` Liang, Kan
2024-01-23 5:30 ` kajoljain
2024-01-23 5:30 ` kajoljain
2024-01-23 5:56 ` Thomas Richter
2024-01-23 5:56 ` Thomas Richter
2024-01-23 14:36 ` Liang, Kan
2024-01-23 14:36 ` Liang, Kan
2024-01-07 4:08 ` Leo Yan
2024-01-07 4:08 ` Leo Yan
2024-01-09 14:01 ` Liang, Kan
2024-01-09 14:01 ` Liang, Kan
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=a0540796-1933-4057-8282-aa219ddda4fe@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=renyu.zj@linux.alibaba.com \
--cc=tmricht@linux.ibm.com \
--cc=will@kernel.org \
--cc=yuhaixin.yhx@linux.alibaba.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.