From: Jiri Olsa <jolsa@redhat.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Petlan <mpetlan@redhat.com>,
Joe Mario <jmario@redhat.com>,
Kan Liang <kan.liang@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Alexey Budankov <alexey.budankov@linux.intel.com>
Subject: Re: [PATCHv2 0/3] perf stat: Add --per-node option
Date: Tue, 5 Nov 2019 14:03:54 +0100 [thread overview]
Message-ID: <20191105130354.GE29390@krava> (raw)
In-Reply-To: <20190904073415.723-1-jolsa@kernel.org>
On Wed, Sep 04, 2019 at 09:34:12AM +0200, Jiri Olsa wrote:
> hi,
> adding --per-node option to aggregate stats per NUMA nodes,
> you can get now use stat command like:
>
> # perf stat -a -I 1000 -e cycles --per-node
> # time node cpus counts unit events
> 1.000542550 N0 20 6,202,097 cycles
> 1.000542550 N1 20 639,559 cycles
> 2.002040063 N0 20 7,412,495 cycles
> 2.002040063 N1 20 2,185,577 cycles
> 3.003451699 N0 20 6,508,917 cycles
> 3.003451699 N1 20 765,607 cycles
> ...
>
> v2 changes:
> - use mallox instead of zalloc plus adding comment [Arnaldo]
> - rename --per-numa to --per-node [Alexey]
> - rename function names to have node instead of numa
>
> Available also in:
> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> perf/fixes
I forgot about this one ;-) rebased the latest perf/core
and pushed out..
thanks,
jirka
>
> thanks,
> jirka
>
>
> ---
> Jiri Olsa (3):
> libperf: Add perf_cpu_map__max function
> perf tools: Add perf_env__numa_node function
> perf stat: Add --per-node agregation support
>
> tools/perf/Documentation/perf-stat.txt | 5 +++++
> tools/perf/builtin-stat.c | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++----------
> tools/perf/lib/cpumap.c | 12 ++++++++++++
> tools/perf/lib/include/perf/cpumap.h | 1 +
> tools/perf/lib/libperf.map | 1 +
> tools/perf/util/cpumap.c | 18 ++++++++++++++++++
> tools/perf/util/cpumap.h | 3 +++
> tools/perf/util/env.c | 40 ++++++++++++++++++++++++++++++++++++++++
> tools/perf/util/env.h | 6 ++++++
> tools/perf/util/stat-display.c | 15 +++++++++++++++
> tools/perf/util/stat.c | 1 +
> tools/perf/util/stat.h | 1 +
> 12 files changed, 153 insertions(+), 10 deletions(-)
next prev parent reply other threads:[~2019-11-05 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 7:34 [PATCHv2 0/3] perf stat: Add --per-node option Jiri Olsa
2019-09-04 7:34 ` [PATCH 1/3] libperf: Add perf_cpu_map__max function Jiri Olsa
2019-09-04 7:34 ` [PATCH 2/3] perf tools: Add perf_env__numa_node function Jiri Olsa
2019-11-12 11:18 ` [tip: perf/core] perf env: Add perf_env__numa_node() tip-bot2 for Jiri Olsa
2019-09-04 7:34 ` [PATCH 3/3] perf stat: Add --per-node agregation support Jiri Olsa
2019-11-12 11:17 ` [tip: perf/core] " tip-bot2 for Jiri Olsa
2019-11-05 13:03 ` Jiri Olsa [this message]
2019-11-05 15:37 ` [PATCHv2 0/3] perf stat: Add --per-node option Arnaldo Carvalho de Melo
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=20191105130354.GE29390@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=jmario@redhat.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@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.