From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Andi Kleen <ak@linux.intel.com>, David Ahern <dsahern@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCHv5 00/22] perf stat: Introduce --per-thread option
Date: Fri, 26 Jun 2015 12:06:44 -0300 [thread overview]
Message-ID: <20150626150644.GC3265@kernel.org> (raw)
In-Reply-To: <1435310967-14570-1-git-send-email-jolsa@kernel.org>
Em Fri, Jun 26, 2015 at 11:29:05AM +0200, Jiri Olsa escreveu:
> hi,
> adding the possibility to display stat data per thread.
>
> Allowing following commands and output:
>
> $ perf stat -e cycles,instructions --per-thread -p 30190,30242
> ^C
> Performance counter stats for process id '30190,30242':
>
> cat-30190 0 cycles
> yes-30242 3,842,525,421 cycles
> cat-30190 0 instructions
> yes-30242 10,370,817,010 instructions
>
> 1.143155657 seconds time elapsed
>
>
> Also works under interval mode:
>
> $ perf stat -e cycles,instructions --per-thread -p 30190,30242 -I 1000
> # time comm-pid counts unit events
Thanks, applied, tested,
- Arnaldo
prev parent reply other threads:[~2015-06-26 15:06 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 9:29 [PATCHv5 00/22] perf stat: Introduce --per-thread option Jiri Olsa
2015-06-26 9:29 ` [PATCH 01/22] perf thread_map: Introduce thread_map__reset function Jiri Olsa
2015-06-26 14:06 ` Arnaldo Carvalho de Melo
2015-06-30 4:52 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 02/22] perf tools: Add comm string into struct thread_map Jiri Olsa
2015-06-30 4:52 ` [tip:perf/urgent] perf thrad_map: Add comm string into array tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 03/22] perf tests: Add thread_map object tests Jiri Olsa
2015-06-30 4:53 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 04/22] perf stat: Introduce perf_counts function Jiri Olsa
2015-06-30 4:53 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 05/22] perf stat: Use xyarray for cpu evsel counts Jiri Olsa
2015-06-30 4:53 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 06/22] perf stat: Make stats work over the thread dimension Jiri Olsa
2015-06-30 4:54 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 07/22] perf stat: Rename struct perf_counts::cpu member to values Jiri Olsa
2015-06-30 4:54 ` [tip:perf/urgent] perf stat: Rename struct perf_counts:: cpu " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 08/22] perf stat: Introduce perf_evlist__reset_stats Jiri Olsa
2015-06-30 4:54 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 09/22] perf stat: Move perf_evsel__(alloc|free|reset)_stat_priv into stat object Jiri Olsa
2015-06-30 4:54 ` [tip:perf/urgent] perf stat: Move perf_evsel__(alloc|free|reset) _stat_priv " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 10/22] perf stat: Move perf_evsel__(alloc|free)_prev_raw_counts " Jiri Olsa
2015-06-30 4:55 ` [tip:perf/urgent] perf stat: Move perf_evsel__(alloc|free) _prev_raw_counts " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 11/22] perf stat: Move perf_evlist__(alloc|free|reset)_stats " Jiri Olsa
2015-06-30 4:55 ` [tip:perf/urgent] perf stat: Move perf_evlist__(alloc|free|reset) _stats " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 12/22] perf stat: Introduce perf_evsel__alloc_stats function Jiri Olsa
2015-06-30 4:55 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 13/22] perf stat: Introduce perf_evsel__read function Jiri Olsa
2015-06-30 4:56 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 14/22] perf stat: Introduce read_counters function Jiri Olsa
2015-06-30 4:56 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 15/22] perf stat: Separate counters reading and processing Jiri Olsa
2015-06-30 4:56 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 16/22] perf stat: Move zero_per_pkg into counter process code Jiri Olsa
2015-06-30 4:57 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 17/22] perf stat: Move perf_stat initialization " Jiri Olsa
2015-06-30 4:57 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 18/22] perf stat: Remove perf_evsel__read_cb function Jiri Olsa
2015-06-30 4:57 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 19/22] perf stat: Rename print_interval to process_interval Jiri Olsa
2015-06-30 4:57 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 20/22] perf stat: Using init_stats instead of memset Jiri Olsa
2015-06-30 4:58 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 21/22] perf stat: Introduce print_counters function Jiri Olsa
2015-06-30 4:58 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 9:29 ` [PATCH 22/22] perf stat: Introduce --per-thread option Jiri Olsa
2015-06-30 4:58 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-26 15:06 ` Arnaldo Carvalho de Melo [this message]
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=20150626150644.GC3265@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox