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 2/3] perf stat: rename --aggr-socket to --per-socket
Date: Thu, 14 Feb 2013 13:57:28 +0100 [thread overview]
Message-ID: <1360846649-6411-3-git-send-email-eranian@google.com> (raw)
In-Reply-To: <1360846649-6411-1-git-send-email-eranian@google.com>
To make it more obvious what this option does as
suggested by Andi on LKML.
Signed-off-by: Stephane Eranian <eranian@google.com>
---
tools/perf/Documentation/perf-stat.txt | 4 ++--
tools/perf/builtin-stat.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/perf/Documentation/perf-stat.txt b/tools/perf/Documentation/perf-stat.txt
index faf4f4f..01117c5 100644
--- a/tools/perf/Documentation/perf-stat.txt
+++ b/tools/perf/Documentation/perf-stat.txt
@@ -119,10 +119,10 @@ perf stat --repeat 10 --null --sync --pre 'make -s O=defconfig-build/clean' -- m
Print count deltas every N milliseconds (minimum: 100ms)
example: perf stat -I 1000 -e cycles -a sleep 5
---aggr-socket::
+--per-socket::
Aggregate counts per processor socket for system-wide mode measurements. This
is a useful mode to detect imbalance between sockets. To enable this mode,
-use --aggr-socket in addition to -a. (system-wide). The output includes the
+use --per-socket in addition to -a. (system-wide). The output includes the
socket number and the number of online processors on that socket. This is
useful to gauge the amount of aggregation.
diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
index a19f8d5..508d9b4 100644
--- a/tools/perf/builtin-stat.c
+++ b/tools/perf/builtin-stat.c
@@ -1357,7 +1357,7 @@ int cmd_stat(int argc, const char **argv, const char *prefix __maybe_unused)
"command to run after to the measured command"),
OPT_UINTEGER('I', "interval-print", &interval,
"print counts at regular interval in ms (>= 100)"),
- OPT_SET_UINT(0, "aggr-socket", &aggr_mode,
+ OPT_SET_UINT(0, "per-socket", &aggr_mode,
"aggregate counts per processor socket", AGGR_SOCKET),
OPT_END()
};
--
1.7.9.5
next prev parent reply other threads:[~2013-02-14 12:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 12:57 [PATCH v2 0/3] perf stat: add per-core count aggregation Stephane Eranian
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 ` Stephane Eranian [this message]
2013-04-02 9:34 ` [tip:perf/core] perf stat: Rename --aggr-socket to --per-socket 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-3-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