From: Manuel Selva <selva.manuel@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Intel PEBS Load Latency Measurement
Date: Tue, 17 Sep 2013 09:44:35 +0200 [thread overview]
Message-ID: <52380863.4090606@insa-lyon.fr> (raw)
Hi all,
I am trying to use PMU on a 2 sockets workstation (2x Intel Xeon X5650
currently running Linux 3.6.11) processor to identify memory controller
unbalance.
For this purpose I successfully used some uncore events to count the
load on each memory controller through the perf_event_open system call.
I am now planning to use Intel PEBS Load Latency Measurement to identify
if these loads result in "unusual" long memory latencies.
Looking at Vince Weaver web page discussing about kernel support for PMU
here:
http://web.eece.maine.edu/~vweaver/projects/perf_events/features.html I
saw that the kernel 3.10 supports Load Latency Measurement.
Unfortunately I can't find a man page describing how this works. Before
looking at kernel sources, I wanted to ask here for confirmation about
Load Latency Measurement in recent Linux kernels.
Can anyone confirm that this functionality is available and usable ? Is
the perf userland tool using it to provide the functionality to end users ?
Thanks in advance for your help,
--
Manu
next reply other threads:[~2013-09-17 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 7:44 Manuel Selva [this message]
2013-09-19 8:22 ` Intel PEBS Load Latency Measurement Andi Kleen
2013-10-28 11:28 ` Manuel Selva
2013-10-29 2:36 ` Namhyung Kim
[not found] ` <CALbiyZy_JE+wai7d_=r-XzE+FdHRitTiAuPmANtRt7Qpet8fTg@mail.gmail.com>
2013-10-29 9:12 ` Fwd: " Manuel Selva
2013-10-29 13:20 ` Manuel Selva
2013-11-01 8:41 ` Namhyung Kim
2013-11-01 9:02 ` Manuel Selva
2013-11-01 17:02 ` Vince Weaver
2013-11-01 18:08 ` Manuel Selva
2013-11-01 8:38 ` Fwd: " Namhyung Kim
2013-11-06 13:06 ` Manuel Selva
2013-11-06 13:41 ` Stephane Eranian
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=52380863.4090606@insa-lyon.fr \
--to=selva.manuel@gmail.com \
--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.