linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 蔡沅信 <fissure2010@gmail.com>
To: Leo Yan <leo.yan@linaro.org>, James Clark <james.clark@arm.com>,
	linux-perf-users@vger.kernel.org,
	Mark Rutland <mark.rutland@arm.com>,
	Suzuki Kuruppassery Poulose <suzuki.poulose@arm.com>
Subject: Re: Some questions about using the perf tool in ARM-SPE
Date: Sat, 1 Jul 2023 13:25:37 +0800	[thread overview]
Message-ID: <CALDTKqivmdU4tFRyc99QUAbGSHG4ttzyuWN7wRRux9KrYdHa0w@mail.gmail.com> (raw)
In-Reply-To: <20230618092806.GA245455@leoy-huanghe.lan>

Hi Leo Yan

On our platform, I cannot enable too many NUMA configurations as it
would lead to build failures.
could this be the reason for c2c failure? If so, I will try to
identify which side is experiencing issues.

This is my platform config status. ccould support c2c?
user_shell:/data/local/tmp # zcat /proc/config.gz | grep NUMA
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
# CONFIG_NUMA is not set
CONFIG_DMA_PERNUMA_CMA=y

> ./perf script --header -I
I think that's a key message.
# ======
# missing features: TRACING_DATA CPUDESC NUMA_TOPOLOGY BRANCH_STACK
GROUP_DESC STAT MEM_TOPOLOGY CLOCKID DIR_FORMAT (null) (null)
COMPRESSED CPU_PMU_CAPS CLOCK_DATA HYBRID_TOPOLOGY
# ========
#
Only instruction-based sampling period is currently supported by Arm SPE.

There are also many events related to L1d, TLB, and memory that are
displayed. If you require this information, I can provide it

         perf6.1  4725 [000]   129.779296:          1
                                                   l1d-access:
ffffffe012888f64 [unknown] ([unknown])

Many Thanks
Best Regards
Zack.
Leo Yan <leo.yan@linaro.org> 於 2023年6月18日 週日 下午5:28寫道:

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
乾淨無病毒。www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

>
> On Wed, Jun 14, 2023 at 02:08:36PM +0800, 蔡沅信 wrote:
> > "Fix mail to text modeFix mail to text mode"
> >
> > Hi,
> > How do I add NUME nodes (or CPU topology) to the kernel config?
>
> Below configurations are enabled in my testing kernel:
>
> root@leoy-huangpu:/home/leoy# zcat /proc/config.gz | grep NUMA
> CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
> CONFIG_NUMA_BALANCING=y
> CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=y
> CONFIG_NUMA=y
> CONFIG_ACPI_NUMA=y
> CONFIG_NUMA_KEEP_MEMINFO=y
> CONFIG_USE_PERCPU_NUMA_NODE_ID=y
> CONFIG_GENERIC_ARCH_NUMA=y
> CONFIG_OF_NUMA=y
> CONFIG_DMA_PERNUMA_CMA=y
>
> > After I modified arm-spe.c. Snoop is working but Locked&Blocked&Local
> > INSTR Latency their results are always No&N/A&0
>
> I cannot understand this ... What's you have modified for arm-spe.c?
>
> If you don't share more complete perf log then it would be difficult to
> understand and locate issue.
>
> > I merged 3 Cluter into one and have been able to record the whole system.
> > user_shell:/sys/bus/event_source/devices/arm_spe_0 # cat cpumask
> > 0-7
>
> This seems to me fine to me.
>
> > On the c2c side:
> > user_shel:/data/local/tmp # ./perf c2c report -vvv
> > coalesce sort   fields: offset,iaddr
> > coalesce resort fields: offset,tot_peer
> > coalesce output fields:
> > cl_num_empty,percent_rmt_peer,percent_lcl_peer,percent_stores_l1hit,percent_stores_l1miss,percent_stores_na,offset,offset_node,dcacheline_count,iaddr,mean_rmt_peer,mean_lcl_peer,mean_load,tot_recs,cpucnt,symbol,dso,cl_srcline,node
> > Failed setup nodes
>
> Before diving into "perf c2c" tool, please use "perf script" tool to
> decode the perf data file and check if you have captured any SPE trace
> data, and it's good to dump header info.  This would be useful to
> analyze the issie.
>
> $ ./perf script --header -I
>
> > On the other hand, the perf I use is statically compiled with the
> > aarch64 cross-compiler. I can't open all the features
>
> This would be fine.  At my side, I built perf statically on x86_64
> machine with the command:
>
> $ make LDFLAGS=-static NO_LIBELF=1 NO_JVMTI=1  VF=1 DEBUG=1 NO_LIBTRACEEVENT=1
>
> And then I copied the perf binary on my Arm64 machine, it works pretty
> well for Arm SPE.
>
> Thanks,
> Leo

  reply	other threads:[~2023-07-01  5:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  7:14 Some questions about using the perf tool in ARM-SPE 蔡沅信
2023-06-09  9:06 ` James Clark
     [not found]   ` <CALDTKqg01+xJ2xu218c_QH2PbX9wdhYOiJfDieCXL5PHWV-6FQ@mail.gmail.com>
     [not found]     ` <77773641-26e5-a754-63cf-e7d3443e11fc@arm.com>
2023-06-13 13:23       ` 蔡沅信
2023-06-14  1:21         ` Leo Yan
     [not found]           ` <CALDTKqgz6=WFs=bMvnFkKv5kt5OP5wtUqQ2uekVbumCxNqeRXw@mail.gmail.com>
2023-06-14  6:08             ` 蔡沅信
2023-06-18  9:28               ` Leo Yan
2023-07-01  5:25                 ` 蔡沅信 [this message]
2023-07-03  8:18           ` Suzuki K Poulose
2023-07-03  8:24             ` James Clark
2023-07-03  9:39               ` Leo Yan
2023-07-03  9:42                 ` James Clark
2023-07-03 10:20                   ` Leo Yan
2023-07-03 13:28                     ` Suzuki K Poulose
2023-07-05 17:33                       ` Namhyung Kim
2023-07-17  5:57                         ` Leo Yan
2023-07-17  9:05                           ` Suzuki K Poulose

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=CALDTKqivmdU4tFRyc99QUAbGSHG4ttzyuWN7wRRux9KrYdHa0w@mail.gmail.com \
    --to=fissure2010@gmail.com \
    --cc=james.clark@arm.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=suzuki.poulose@arm.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 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).