From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: German Gomez <german.gomez@arm.com>,
Ali Saidi <alisaidi@amazon.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, benh@kernel.crashing.org,
Nick.Forrington@arm.com, alexander.shishkin@linux.intel.com,
andrew.kilroy@arm.com, james.clark@arm.com,
john.garry@huawei.com, jolsa@kernel.org, kjain@linux.ibm.com,
lihuafei1@huawei.com, mark.rutland@arm.com,
mathieu.poirier@linaro.org, mingo@redhat.com,
namhyung@kernel.org, peterz@infradead.org, will@kernel.org
Subject: Re: [PATCH v5 5/5] perf mem: Support mem_lvl_num in c2c command
Date: Wed, 20 Apr 2022 13:47:46 -0300 [thread overview]
Message-ID: <YmA5MqWxxLCp1Nff@kernel.org> (raw)
In-Reply-To: <20220420084823.GE843168@leoy-ThinkPad-X240s>
Em Wed, Apr 20, 2022 at 04:48:23PM +0800, Leo Yan escreveu:
> On Mon, Apr 11, 2022 at 11:04:28AM +0100, German Gomez wrote:
> >
> > On 08/04/2022 20:53, Ali Saidi wrote:
> > > In addition to summarizing data encoded in mem_lvl also support data
> > > encoded in mem_lvl_num.
> > >
> > > Since other architectures don't seem to populate the mem_lvl_num field
> > > here there shouldn't be a change in functionality.
> > >
> > > Signed-off-by: Ali Saidi <alisaidi@amazon.com>
> > > ---
> > > tools/perf/util/mem-events.c | 11 +++++++----
> > > 1 file changed, 7 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/tools/perf/util/mem-events.c b/tools/perf/util/mem-events.c
> > > index ed0ab838bcc5..e5e405185498 100644
> > > --- a/tools/perf/util/mem-events.c
> > > +++ b/tools/perf/util/mem-events.c
> > > @@ -485,6 +485,7 @@ int c2c_decode_stats(struct c2c_stats *stats, struct mem_info *mi)
> > > u64 daddr = mi->daddr.addr;
> > > u64 op = data_src->mem_op;
> > > u64 lvl = data_src->mem_lvl;
> > > + u64 lnum = data_src->mem_lvl_num;
> > > u64 snoop = data_src->mem_snoop;
> > > u64 lock = data_src->mem_lock;
> > > u64 blk = data_src->mem_blk;
> > > @@ -527,16 +528,18 @@ do { \
> > > if (lvl & P(LVL, UNC)) stats->ld_uncache++;
> > > if (lvl & P(LVL, IO)) stats->ld_io++;
> > > if (lvl & P(LVL, LFB)) stats->ld_fbhit++;
> >
> > Just for completion, can we also handle LFB as it seems to be being set
> > in "/arch/x86/events/intel/ds.c"? (Sorry I missed this in the v4)
>
> With fixing LFB issue pointed by German, the change looks good to me:
Waiting for a v6 then, please collect Leo's reviewed-by tag when
submitting it.
- Arnaldo
> Reviewed-by: Leo Yan <leo.yan@linaro.org>
>
> It would be appreciate if x86 or PowerPC maintainers could take a look
> for this patch. Thanks!
> Leo
>
> > > - if (lvl & P(LVL, L1 )) stats->ld_l1hit++;
> > > - if (lvl & P(LVL, L2 )) stats->ld_l2hit++;
> > > - if (lvl & P(LVL, L3 )) {
> > > + if (lvl & P(LVL, L1) || lnum == P(LVLNUM, L1))
> > > + stats->ld_l1hit++;
> > > + if (lvl & P(LVL, L2) || lnum == P(LVLNUM, L2))
> > > + stats->ld_l2hit++;
> > > + if (lvl & P(LVL, L3) || lnum == P(LVLNUM, L3)) {
> > > if (snoop & P(SNOOP, HITM))
> > > HITM_INC(lcl_hitm);
> > > else
> > > stats->ld_llchit++;
> > > }
> > >
> > > - if (lvl & P(LVL, LOC_RAM)) {
> > > + if (lvl & P(LVL, LOC_RAM) || lnum == P(LVLNUM, RAM)) {
> > > stats->lcl_dram++;
> > > if (snoop & P(SNOOP, HIT))
> > > stats->ld_shared++;
--
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: German Gomez <german.gomez@arm.com>,
Ali Saidi <alisaidi@amazon.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, benh@kernel.crashing.org,
Nick.Forrington@arm.com, alexander.shishkin@linux.intel.com,
andrew.kilroy@arm.com, james.clark@arm.com,
john.garry@huawei.com, jolsa@kernel.org, kjain@linux.ibm.com,
lihuafei1@huawei.com, mark.rutland@arm.com,
mathieu.poirier@linaro.org, mingo@redhat.com,
namhyung@kernel.org, peterz@infradead.org, will@kernel.org
Subject: Re: [PATCH v5 5/5] perf mem: Support mem_lvl_num in c2c command
Date: Wed, 20 Apr 2022 13:47:46 -0300 [thread overview]
Message-ID: <YmA5MqWxxLCp1Nff@kernel.org> (raw)
In-Reply-To: <20220420084823.GE843168@leoy-ThinkPad-X240s>
Em Wed, Apr 20, 2022 at 04:48:23PM +0800, Leo Yan escreveu:
> On Mon, Apr 11, 2022 at 11:04:28AM +0100, German Gomez wrote:
> >
> > On 08/04/2022 20:53, Ali Saidi wrote:
> > > In addition to summarizing data encoded in mem_lvl also support data
> > > encoded in mem_lvl_num.
> > >
> > > Since other architectures don't seem to populate the mem_lvl_num field
> > > here there shouldn't be a change in functionality.
> > >
> > > Signed-off-by: Ali Saidi <alisaidi@amazon.com>
> > > ---
> > > tools/perf/util/mem-events.c | 11 +++++++----
> > > 1 file changed, 7 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/tools/perf/util/mem-events.c b/tools/perf/util/mem-events.c
> > > index ed0ab838bcc5..e5e405185498 100644
> > > --- a/tools/perf/util/mem-events.c
> > > +++ b/tools/perf/util/mem-events.c
> > > @@ -485,6 +485,7 @@ int c2c_decode_stats(struct c2c_stats *stats, struct mem_info *mi)
> > > u64 daddr = mi->daddr.addr;
> > > u64 op = data_src->mem_op;
> > > u64 lvl = data_src->mem_lvl;
> > > + u64 lnum = data_src->mem_lvl_num;
> > > u64 snoop = data_src->mem_snoop;
> > > u64 lock = data_src->mem_lock;
> > > u64 blk = data_src->mem_blk;
> > > @@ -527,16 +528,18 @@ do { \
> > > if (lvl & P(LVL, UNC)) stats->ld_uncache++;
> > > if (lvl & P(LVL, IO)) stats->ld_io++;
> > > if (lvl & P(LVL, LFB)) stats->ld_fbhit++;
> >
> > Just for completion, can we also handle LFB as it seems to be being set
> > in "/arch/x86/events/intel/ds.c"? (Sorry I missed this in the v4)
>
> With fixing LFB issue pointed by German, the change looks good to me:
Waiting for a v6 then, please collect Leo's reviewed-by tag when
submitting it.
- Arnaldo
> Reviewed-by: Leo Yan <leo.yan@linaro.org>
>
> It would be appreciate if x86 or PowerPC maintainers could take a look
> for this patch. Thanks!
> Leo
>
> > > - if (lvl & P(LVL, L1 )) stats->ld_l1hit++;
> > > - if (lvl & P(LVL, L2 )) stats->ld_l2hit++;
> > > - if (lvl & P(LVL, L3 )) {
> > > + if (lvl & P(LVL, L1) || lnum == P(LVLNUM, L1))
> > > + stats->ld_l1hit++;
> > > + if (lvl & P(LVL, L2) || lnum == P(LVLNUM, L2))
> > > + stats->ld_l2hit++;
> > > + if (lvl & P(LVL, L3) || lnum == P(LVLNUM, L3)) {
> > > if (snoop & P(SNOOP, HITM))
> > > HITM_INC(lcl_hitm);
> > > else
> > > stats->ld_llchit++;
> > > }
> > >
> > > - if (lvl & P(LVL, LOC_RAM)) {
> > > + if (lvl & P(LVL, LOC_RAM) || lnum == P(LVLNUM, RAM)) {
> > > stats->lcl_dram++;
> > > if (snoop & P(SNOOP, HIT))
> > > stats->ld_shared++;
--
- Arnaldo
_______________________________________________
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:[~2022-04-20 16:47 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 19:53 [PATCH v4 0/4] perf: arm-spe: Decode SPE source and use for perf c2c Ali Saidi
2022-04-08 19:53 ` Ali Saidi
2022-04-08 19:53 ` [PATCH v5 1/5] tools: arm64: Import cputype.h Ali Saidi
2022-04-08 19:53 ` Ali Saidi
2022-04-18 14:57 ` Leo Yan
2022-04-18 14:57 ` Leo Yan
2022-04-08 19:53 ` [PATCH v5 2/5] perf: Add SNOOP_PEER flag to perf mem data struct Ali Saidi
2022-04-08 19:53 ` Ali Saidi
2022-04-20 8:20 ` Leo Yan
2022-04-20 8:20 ` Leo Yan
2022-04-20 18:43 ` Liang, Kan
2022-04-20 18:43 ` Liang, Kan
2022-04-22 18:49 ` Ali Saidi
2022-04-22 18:49 ` Ali Saidi
2022-04-22 21:08 ` Liang, Kan
2022-04-22 21:08 ` Liang, Kan
2022-04-22 21:22 ` Ali Saidi
2022-04-22 21:22 ` Ali Saidi
2022-04-23 6:38 ` Leo Yan
2022-04-23 6:38 ` Leo Yan
2022-04-23 12:53 ` Andi Kleen
2022-04-23 12:53 ` Andi Kleen
2022-04-24 11:43 ` Leo Yan
2022-04-24 11:43 ` Leo Yan
2022-04-25 17:01 ` Liang, Kan
2022-04-25 17:01 ` Liang, Kan
2022-04-27 16:19 ` Leo Yan
2022-04-27 16:19 ` Leo Yan
2022-04-27 19:29 ` Liang, Kan
2022-04-27 19:29 ` Liang, Kan
2022-04-29 9:28 ` Leo Yan
2022-04-29 9:28 ` Leo Yan
2022-04-08 19:53 ` [PATCH v5 3/5] perf tools: sync addition of PERF_MEM_SNOOPX_PEER Ali Saidi
2022-04-08 19:53 ` Ali Saidi
2022-04-11 10:26 ` German Gomez
2022-04-11 10:26 ` German Gomez
2022-04-11 14:35 ` German Gomez
2022-04-11 14:35 ` German Gomez
2022-04-20 8:23 ` Leo Yan
2022-04-20 8:23 ` Leo Yan
2022-04-08 19:53 ` [PATCH v5 4/5] perf arm-spe: Use SPE data source for neoverse cores Ali Saidi
2022-04-08 19:53 ` Ali Saidi
2022-04-20 8:30 ` Leo Yan
2022-04-20 8:30 ` Leo Yan
2022-04-20 8:42 ` Leo Yan
2022-04-20 8:42 ` Leo Yan
2022-04-08 19:53 ` [PATCH v5 5/5] perf mem: Support mem_lvl_num in c2c command Ali Saidi
2022-04-08 19:53 ` Ali Saidi
2022-04-11 10:04 ` German Gomez
2022-04-11 10:04 ` German Gomez
2022-04-20 8:48 ` Leo Yan
2022-04-20 8:48 ` Leo Yan
2022-04-20 16:47 ` Arnaldo Carvalho de Melo [this message]
2022-04-20 16:47 ` Arnaldo Carvalho de Melo
2022-04-20 19:02 ` Liang, Kan
2022-04-20 19:02 ` 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=YmA5MqWxxLCp1Nff@kernel.org \
--to=acme@kernel.org \
--cc=Nick.Forrington@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alisaidi@amazon.com \
--cc=andrew.kilroy@arm.com \
--cc=benh@kernel.crashing.org \
--cc=german.gomez@arm.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=lihuafei1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@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.