From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ian Rogers <irogers@google.com>,
Fangrui Song <maskray@google.com>,
Chang Rui <changruinj@gmail.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] perf symbol: Correct address for bss symbols
Date: Tue, 26 Jul 2022 08:53:07 +0800 [thread overview]
Message-ID: <20220726005307.GA36862@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <Yt7hGepLBAJJuvII@kernel.org>
Hi Arnaldo,
On Mon, Jul 25, 2022 at 03:29:45PM -0300, Arnaldo Carvalho de Melo wrote:
[...]
> > First we used 'perf mem record' to run the test program and then used
> > 'perf --debug verbose=4 mem report' to observe what's the symbol info
> > for 'buf1' and 'buf2' structures.
> >
> > # ./perf mem record -e ldlat-loads,ldlat-stores -- false_sharing.exe 8
>
> Can you share the source code for your false sharing proggie? We need to
> have something in 'perf test' exercising these routines :-)
Sure, I am using the false sharing test case:
https://github.com/joemario/perf-c2c-usage-files/blob/master/false_sharing_example.c
... with build command:
$ gcc -g false_sharing_example.c -pthread -lnuma -o false_sharing.exe
Do want me to proceed for adding test case? Otherwise, it's fine if
you will work on the enabling test case :)
Thanks,
Leo
next prev parent reply other threads:[~2022-07-26 0:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 6:00 [PATCH v3 0/2] perf symbol: Minor fixing Leo Yan
2022-07-24 6:00 ` [PATCH v3 1/2] perf symbol: Correct address for bss symbols Leo Yan
2022-07-25 18:29 ` Arnaldo Carvalho de Melo
2022-07-26 0:53 ` Leo Yan [this message]
2022-07-26 1:04 ` Arnaldo Carvalho de Melo
2022-07-26 1:06 ` Leo Yan
2022-07-30 5:13 ` Ian Rogers
2022-07-30 9:38 ` Leo Yan
2022-07-30 15:21 ` Ian Rogers
2022-07-31 12:37 ` Leo Yan
2022-07-31 16:51 ` Ian Rogers
2022-07-24 6:00 ` [PATCH v3 2/2] perf symbol: Skip symbols if SHF_ALLOC flag is not set Leo Yan
2022-07-25 16:54 ` [PATCH v3 0/2] perf symbol: Minor fixing Namhyung Kim
2022-07-26 0:55 ` 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=20220726005307.GA36862@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=changruinj@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maskray@google.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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