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 v2 0/3] perf stat: add per-core count aggregation
Date: Thu, 14 Feb 2013 13:57:26 +0100 [thread overview]
Message-ID: <1360846649-6411-1-git-send-email-eranian@google.com> (raw)
This patch series contains improvement to the aggregation support
in perf stat.
First, the aggregation code is refactored and a aggr_mode enum
is defined. There is also an important bug fix for the existing
per-socket aggregation.
Second, the option --aggr-socket is renamed --per-socket.
Third, the patch adds a new --per-core option to perf stat.
It aggregates counts per physical core and becomes useful on
systems with hyper-threading. The cores are presented per
socket: S0-C1, means socket 0 core 1. Note that the core number
represents its physical core id. As such, numbers may not always
be contiguous. All of this is based on topology information available
in sysfs.
Per-core aggregation can be combined with interval printing:
# perf stat -a --per-core -I 1000 -e cycles sleep 100
# time core cpus counts events
1.000101160 S0-C0 2 6,051,254,899 cycles
1.000101160 S0-C1 2 6,379,230,776 cycles
1.000101160 S0-C2 2 6,480,268,471 cycles
1.000101160 S0-C3 2 6,110,514,321 cycles
2.000663750 S0-C0 2 6,572,533,016 cycles
2.000663750 S0-C1 2 6,378,623,674 cycles
2.000663750 S0-C2 2 6,264,127,589 cycles
2.000663750 S0-C3 2 6,305,346,613 cycles
For instance here on this SNB machine, we can see that the load
is evenly balanced across all 4 physical core (HT is on).
In v2, we print events across all cores or socket and we renamed
--aggr-socket to --per-socket and renamed --aggr-core to --per-core
Signed-off-by: Stephane Eranian <eranian@google.com>
Stephane Eranian (3):
perf stat: refactor aggregation code
perf stat: rename --aggr-socket to --per-socket
perf stat: add per-core aggregation
tools/perf/Documentation/perf-stat.txt | 10 +-
tools/perf/builtin-stat.c | 237 ++++++++++++++++++++------------
tools/perf/util/cpumap.c | 86 ++++++++++--
tools/perf/util/cpumap.h | 12 ++
4 files changed, 241 insertions(+), 104 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-02-14 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 12:57 Stephane Eranian [this message]
2013-02-14 12:57 ` [PATCH v2 1/3] perf stat: refactor aggregation code Stephane Eranian
2013-03-07 21:38 ` Jiri Olsa
2013-03-25 16:22 ` Arnaldo Carvalho de Melo
2013-04-02 9:33 ` [tip:perf/core] perf stat: Refactor " tip-bot for Stephane Eranian
2013-02-14 12:57 ` [PATCH v2 2/3] perf stat: rename --aggr-socket to --per-socket Stephane Eranian
2013-04-02 9:34 ` [tip:perf/core] perf stat: Rename " tip-bot for Stephane Eranian
2013-02-14 12:57 ` [PATCH v2 3/3] perf stat: add per-core aggregation Stephane Eranian
2013-04-02 9:36 ` [tip:perf/core] perf stat: Add " tip-bot for Stephane Eranian
2013-03-07 16:22 ` [PATCH v2 0/3] perf stat: add per-core count aggregation Stephane Eranian
2013-03-25 13:57 ` 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=1360846649-6411-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 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.