From: Leo Yan <leo.yan@linux.dev>
To: James Clark <james.clark@arm.com>
Cc: Ian Rogers <irogers@google.com>,
"?????? (Baisheng Gao)" <baisheng.gao@unisoc.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"???? (Hao_hao Wang)" <Hao_hao.Wang@unisoc.com>
Subject: Re: Question about using the perf c2c in UMA system
Date: Wed, 1 May 2024 03:32:50 +0800 [thread overview]
Message-ID: <20240430193250.GC125@debian-dev> (raw)
In-Reply-To: <40bd4bb1-a2fa-4173-aea8-8ccd3ca23df3@arm.com>
On Tue, Apr 30, 2024 at 03:36:02PM +0100, James Clark wrote:
[...]
> >> On Mon, Apr 08, 2024 at 10:52:59AM +0000, ?????? (Baisheng Gao) wrote:
> >>> Hi linux-perf-users,
> >>>
> >>> My perf tool version is 6.6, and I compiled it to run on an Android system.
> >>> The problem is:
> >>>
> >>> # ./perf c2c report
> >>> Failed setup nodes
> >>>
> >>> According to the articles on the Internet, it seems that the perf c2c is only supported
> >>> in NUMA system. However, the cache false sharing does not exist only in NUMA, and
> >>> the UMA system has also the problem. So I wonder how to support perf c2c in UMA.
> >>
> >> The log above is related with parsing NUMA nodes, but this doesn't
> >> mean 'perf c2c' must run on NUMA system. My understanding is both
> >> x86_64 (memory event) and Arm64 (SPE) support 'perf c2c' not only on
> >> NUMA.
> >
> > The lack of SPE on most ARM hardware really is a pain. Can we add a
> > better error message to make it clearer to users that they need a
> > neoverse CPU? :-)
We cannot stick to Arm Neoverse CPUs as Arm SPE is supported on more CPU
variants. On the other hand, I think we need to dynamically detect CPU
feature for SPE to replace current code for binding specific CPU
variants.
> This issue seems to be about report rather than record, so I'm assuming
> that the record worked and SPE is present.
Yes, this issue is for the report command.
@Baisheng, do you mind to share the steps for reproduce this issue or
drop the perf data file with me? Sorry if I missed your sharing.
> Having said that, the error message for no SPE isn't great, but it's not
> that bad either:
>
> $ perf c2c record
> failed: no PMU supports the memory events
This is better than nothing ;-) I will check a bit for a better log.
Thanks,
Leo
prev parent reply other threads:[~2024-04-30 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <80f723d230744bc299044cfd4f8c4d92@shmbx06.spreadtrum.com>
2024-04-29 21:43 ` Question about using the perf c2c in UMA system Leo Yan
2024-04-30 3:40 ` Ian Rogers
2024-04-30 14:36 ` James Clark
2024-04-30 19:32 ` Leo Yan [this message]
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=20240430193250.GC125@debian-dev \
--to=leo.yan@linux.dev \
--cc=Hao_hao.Wang@unisoc.com \
--cc=baisheng.gao@unisoc.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.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.