From: Stephane Eranian <eranian@google.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@elte.hu, ak@linux.intel.com,
acme@redhat.com, jolsa@redhat.com, namhyung.kim@lge.com
Subject: [PATCH 0/2] perf: add new uncore command
Date: Thu, 31 Jan 2013 14:54:37 +0100 [thread overview]
Message-ID: <1359640479-5289-1-git-send-email-eranian@google.com> (raw)
This patchset adds a new command to perf: perf uncore.
It is used to measure processor socket-level metrics
on a system-wide basis and at all priv levels.
The command comes with a set of predefined key metrics
which are useful to measure multi-socket system imbalance
and various bandwidths.
The following metrics are currently defined:
- memory bandwidth (Nehalem, Westmere, SandyBridge-EP)
- PCIe bandwidth (SandyBridge-EP)
- QPI bandwidth (SandyBridge-EP)
- C-state residency (SandyBridge-EP)
Others can be added in the future.
The command provides options to modify the unit of the metrics
(default: MB/s for bandwidth).
Example on Nehalem:
# perf uncore
#------------------------------
# Socket0 |
#------------------------------
# RAM Bandwidth |
# Wr Rd|
# MB/s MB/s|
#------------------------------
4954.99 14897.29
4953.97 14894.56
4947.52 14874.97
To make plotting easier, the output can be augmented with a timestamp:
# perf uncore -T
#----------------------------------------
# | Socket0 |
# |------------------------------
# Time | RAM Bandwidth |
# in | Wr Rd|
# secs | MB/s MB/s|
#----------------------------------------
1 4952.50 14890.49
2 4955.55 14900.19
3 4949.13 14879.60
4 4954.66 14896.26
The code is split between generic layer (builtin-uncore.c) and
an arch specific layer (arch/*/util/uncore.c). All events are
hardcoded because they don't change for a given processor and
metric computation requires combining multiple events.
Signed-off-by: Stephane Eranian <eranian@google.com>
---
Stephane Eranian (2):
perf tools: add cpu_map__get_socket()
perf: add new perf uncore command
tools/perf/Documentation/perf-uncore.txt | 88 ++++
tools/perf/Makefile | 1 +
tools/perf/arch/x86/Makefile | 1 +
tools/perf/arch/x86/util/uncore.c | 539 ++++++++++++++++++++++
tools/perf/builtin-uncore.c | 739 ++++++++++++++++++++++++++++++
tools/perf/builtin.h | 1 +
tools/perf/command-list.txt | 1 +
tools/perf/perf.c | 1 +
tools/perf/util/cpumap.c | 26 ++
tools/perf/util/cpumap.h | 1 +
tools/perf/util/uncore.h | 56 +++
11 files changed, 1454 insertions(+)
create mode 100644 tools/perf/Documentation/perf-uncore.txt
create mode 100644 tools/perf/arch/x86/util/uncore.c
create mode 100644 tools/perf/builtin-uncore.c
create mode 100644 tools/perf/util/uncore.h
--
1.7.10.4
next reply other threads:[~2013-01-31 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 13:54 Stephane Eranian [this message]
2013-01-31 13:54 ` [PATCH 1/2] perf tools: add cpu_map__get_socket() Stephane Eranian
2013-01-31 13:54 ` [PATCH 2/2] perf: add new perf uncore command Stephane Eranian
2013-02-01 8:45 ` Namhyung Kim
2013-01-31 14:21 ` [PATCH 0/2] perf: add new " Ingo Molnar
2013-01-31 14:32 ` Stephane Eranian
2013-02-01 8:42 ` Namhyung Kim
2013-02-02 1:35 ` Andi Kleen
2013-02-04 13:33 ` Jiri Olsa
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=1359640479-5289-1-git-send-email-eranian@google.com \
--to=eranian@google.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--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