From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
Cc: linux-perf-users@vger.kernel.org,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Subject: Re: perf tool: perf mem not working on s390x
Date: Fri, 23 Jun 2017 15:33:04 -0300 [thread overview]
Message-ID: <20170623183304.GF4622@kernel.org> (raw)
In-Reply-To: <4ad64b13-5ed4-a8f0-9a3a-2748663bb5a2@linux.vnet.ibm.com>
Em Fri, Jun 23, 2017 at 09:28:53AM +0200, Thomas-Mich Richter escreveu:
>
> When I run perf mem ... it fails with
>
> [root@s8360046 perf]# ./perf mem record -- sleep 1
> failed: memory events not supported
> [root@s8360046 perf]
>
> That is currently not working on s390.
> When I look into the code, the perf mem command is looking for sysfs files in
>
> -r--r--r-- 1 root root 4096 Jun 9 11:02 /sys/devices/cpu/events/mem-loads
> -r--r--r-- 1 root root 4096 Jun 9 11:02 /sys/devices/cpu/events/mem-stores
>
> Those 2 sysfs files do not exist on a s390. In fact there is a different
> subdirectory tree.
>
> I am not sure how this is handled on the s390 at all. I would have expected
> perf mem to somehow retrieve the event numbers and then feed perf record
> with these event numbers.
> Any comments/ideas on how to handle this?
Humm, IIRC perf mem depends on features present only on x86_64, i.e.
mem access features in x86's latest PEBS.
One would have to look for something equivalent in other architectures
to be able to write the necessary glue.
Probably we should just make it available on the arches that have the
necessary hardware facilities.
- Arnaldo
prev parent reply other threads:[~2017-06-23 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 7:28 perf tool: perf mem not working on s390x Thomas-Mich Richter
2017-06-23 18:33 ` Arnaldo Carvalho de Melo [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=20170623183304.GF4622@kernel.org \
--to=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=tmricht@linux.vnet.ibm.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).