From: Ali Saidi <alisaidi@amazon.com>
To: <german.gomez@arm.com>
Cc: <Nick.Forrington@arm.com>, <acme@kernel.org>,
<alexander.shishkin@linux.intel.com>, <alisaidi@amazon.com>,
<andrew.kilroy@arm.com>, <benh@kernel.crashing.org>,
<james.clark@arm.com>, <john.garry@huawei.com>,
<jolsa@kernel.org>, <kjain@linux.ibm.com>, <leo.yan@linaro.org>,
<lihuafei1@huawei.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <mark.rutland@arm.com>,
<mathieu.poirier@linaro.org>, <mingo@redhat.com>,
<namhyung@kernel.org>, <peterz@infradead.org>, <will@kernel.org>
Subject: Re: [PATCH v7 5/5] perf arm-spe: Use SPE data source for neoverse cores
Date: Wed, 4 May 2022 16:22:20 +0000 [thread overview]
Message-ID: <20220504162220.28528-1-alisaidi@amazon.com> (raw)
In-Reply-To: <458a2de1-dc93-7e2d-5dc5-fbcd670572b6@arm.com>
Hi German,
Thanks for taking another look!
On Tue, 3 May 2022 09:58:15 +0000, German Gomez wrote:
> Hi Ali, Leo
>
> Some minor comments below.
>
> On 26/04/2022 14:59, Ali Saidi wrote:
> > When synthesizing data from SPE, augment the type with source information
> > for Arm Neoverse cores. The field is IMPLDEF but the Neoverse cores all use
> > the same encoding. I can't find encoding information for any other SPE
> > implementations to unify their choices with Arm's thus that is left for
> > future work.
> >
> > This change populates the mem_lvl_num for Neoverse cores as well as the
> > deprecated mem_lvl namespace.
> >
> > Signed-off-by: Ali Saidi <alisaidi@amazon.com>
> > ---
> > .../util/arm-spe-decoder/arm-spe-decoder.c | 1 +
> > .../util/arm-spe-decoder/arm-spe-decoder.h | 12 ++
> > tools/perf/util/arm-spe.c | 130 +++++++++++++++---
> > 3 files changed, 127 insertions(+), 16 deletions(-)
> >
> [snip]
> > + /*
> > + * We have no data on the hit level or data source for stores in the
> > + * Neoverse SPE records.
> > + */
> > + if (record->op & ARM_SPE_ST) {
> > + data_src->mem_lvl = PERF_MEM_LVL_NA;
> > + data_src->mem_lvl_num = PERF_MEM_LVLNUM_ANY_CACHE;
>
> Is it correct to use ANY_CACHE as the NA value? The LVLNUM_* enum begins at 1, so it looks like this should be set to 0 instead (like in HOPS_*).
I think you're making a good point here. To be consistent we should set
mem_lvl_num to PERF_MEM_LVLNUM_NA just like mem_lvl.
Thanks,
Ali
next prev parent reply other threads:[~2022-05-04 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 13:59 [PATCH v4 0/4] perf: arm-spe: Decode SPE source and use for perf c2c Ali Saidi
2022-04-26 13:59 ` [PATCH v7 1/5] perf: Add SNOOP_PEER flag to perf mem data struct Ali Saidi
2022-04-26 13:59 ` [PATCH v7 2/5] perf tools: sync addition of PERF_MEM_SNOOPX_PEER Ali Saidi
2022-04-26 13:59 ` [PATCH v7 3/5] perf mem: Print snoop peer flag Ali Saidi
2022-04-26 13:59 ` [PATCH v7 4/5] perf arm-spe: Don't set data source if it's not a memory operation Ali Saidi
2022-05-03 10:20 ` German Gomez
2022-04-26 13:59 ` [PATCH v7 5/5] perf arm-spe: Use SPE data source for neoverse cores Ali Saidi
2022-04-27 15:59 ` Leo Yan
2022-05-03 9:58 ` German Gomez
2022-05-04 16:22 ` Ali Saidi [this message]
2022-05-05 15:12 ` Leo Yan
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=20220504162220.28528-1-alisaidi@amazon.com \
--to=alisaidi@amazon.com \
--cc=Nick.Forrington@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®