From: Daniel Ortiz <daniel.ortiz@tum.de>
To: linux-perf-users@vger.kernel.org
Subject: perf top for memory access profiling
Date: Tue, 7 Jul 2015 12:20:57 +0000 (UTC) [thread overview]
Message-ID: <mngg78$ft9$1@ger.gmane.org> (raw)
Hello
Right now I am interested in profiling memory accesses. So far I have
used perf mem record (perf mem record -W -d -e "cpu/mem-loads/pp") and
then perf mem report to get information about the address being
accessed, the access latency and the type of access such as l1,l2,l3 and
remote hit or miss. This information would correspon to the fields
"Local", "Weight, "Memory access" and "Data symbol" that are shown by
the default in perf mem report.
I need to move to solution that shows the sampled information right as
it is retrived from the hardware without user intervention, just like
perf top does. Howewer, it seems that perf top does not show such
information with memory access sampling, I have tried doiing the
following :
I started trying to run perf mem record -W -d -e "cpu/mem-loads/pp" but
then I realized that perf top does not support the -d and -W option in
the same way perf record does, what I did was changing the top struct in
the cmd_top functions more specifically the
top.record_opts.sample_address and top.record_opts.sample_weight fields
but the required information is still not shown.
The question is whether you know if perf top is capable in any way of
showing the same information that perf mem report shows even if some
tweaks are necessary.
Kind regards...
Daniel Ortiz
reply other threads:[~2015-07-07 12:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='mngg78$ft9$1@ger.gmane.org' \
--to=daniel.ortiz@tum.de \
--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 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).