From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@intel.com
Cc: acme@kernel.org, a.p.zijlstra@chello.nl, mingo@redhat.com,
jolsa@kernel.org, namhyung@kernel.org, ak@linux.intel.com,
eranian@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 03/10] perf,tools: support option --socket
Date: Thu, 20 Aug 2015 11:30:28 +0200 [thread overview]
Message-ID: <20150820093028.GA4640@krava.brq.redhat.com> (raw)
In-Reply-To: <1439889946-28986-4-git-send-email-kan.liang@intel.com>
On Tue, Aug 18, 2015 at 05:25:39AM -0400, kan.liang@intel.com wrote:
> From: Kan Liang <kan.liang@intel.com>
>
> Introduce a new option for perf report to show the event information in
> the same socket together.
> When this option is set, perf report will force to sort by socket.
>
> $ perf report --stdio --socket
> # To display the perf.data header info, please use
> --header/--header-only options.
> #
> #
> # Total Lost Samples: 0
> #
> # Samples: 686 of event 'cycles'
> # Event count (approx.): 349215462
> #
> #
> # Socket: 0
> #
> # Overhead Command Shared Object Symbol
> # ........ ......... ................
> .................................
> #
> 97.05% test test [.] plusB_c
> 0.98% test test [.] plusA_c
> 0.16% test [kernel.vmlinux] [k] add_mm_counter_fast
> 0.15% swapper [kernel.vmlinux] [k] note_gp_changes
> 0.15% perf [kernel.vmlinux] [k] unmap_single_vma
> 0.06% perf [kernel.vmlinux] [k] run_timer_softirq
> 0.00% swapper [kernel.vmlinux] [k] native_write_msr
> #
> # Socket: 1
> #
> # Overhead Command Shared Object Symbol
> # ........ ......... ................
> .................................
> #
> 0.93% perf [kernel.vmlinux] [k] smp_call_function_single
> 0.19% perf [kernel.vmlinux] [k] page_fault
> 0.19% swapper [kernel.vmlinux] [k] pm_qos_request
> 0.12% rcu_sched [kernel.vmlinux] [k]
> dyntick_save_progress_counter
> 0.00% swapper [kernel.vmlinux] [k] wake_up_process
> 0.00% swapper [kernel.vmlinux] [k] __do_softirq
> 0.00% swapper [kernel.vmlinux] [k] run_timer_softirq
> 0.00% swapper [kernel.vmlinux] [k] native_write_msr
> 0.00% perf [kernel.vmlinux] [k] native_write_msr
nice, but should this be handled by HIST_FILTER__* stuff?
also having generic ability to 'zoom' in TUI for SOCKET/CPU
would be great.. it's already there for thread and dso
jirka
next prev parent reply other threads:[~2015-08-20 9:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 9:25 [PATCH RFC 00/10] stat read during perf sampling kan.liang
2015-08-18 9:25 ` [PATCH RFC 01/10] perf,tools: open event on evsel cpus and threads kan.liang
2015-08-20 8:57 ` Jiri Olsa
2015-08-20 17:24 ` Liang, Kan
2015-08-21 7:43 ` Jiri Olsa
2015-08-21 13:24 ` Liang, Kan
2015-08-18 9:25 ` [PATCH RFC 02/10] perf,tools: Support new sort type --socket kan.liang
2015-08-20 9:09 ` Jiri Olsa
2015-08-21 20:25 ` Liang, Kan
2015-08-23 22:00 ` Jiri Olsa
2015-08-24 14:22 ` Liang, Kan
2015-08-24 14:27 ` Jiri Olsa
2015-08-24 16:47 ` Liang, Kan
2015-08-24 19:30 ` Jiri Olsa
2015-08-27 18:24 ` Jiri Olsa
2015-08-27 18:29 ` Liang, Kan
2015-08-18 9:25 ` [PATCH RFC 03/10] perf,tools: support option --socket kan.liang
2015-08-18 17:36 ` Stephane Eranian
2015-08-20 9:30 ` Jiri Olsa [this message]
2015-08-18 9:25 ` [PATCH RFC 04/10] perf,tools: Add 'N' event/group modifier kan.liang
2015-08-18 9:25 ` [PATCH RFC 05/10] perf,tools: Enable statistic read for perf record kan.liang
2015-08-20 9:39 ` Jiri Olsa
2015-08-20 9:41 ` Jiri Olsa
2015-08-18 9:25 ` [PATCH RFC 06/10] perf,tools: New RECORD type PERF_RECORD_STAT_READ kan.liang
2015-08-20 9:49 ` Jiri Olsa
2015-08-18 9:25 ` [PATCH RFC 07/10] perf,tools: record counter statistics during sampling kan.liang
2015-08-18 9:25 ` [PATCH RFC 08/10] perf,tools: option to set stat read interval kan.liang
2015-08-18 9:25 ` [PATCH RFC 09/10] perf,tools: don't validate non-sample event kan.liang
2015-08-18 9:25 ` [PATCH RFC 10/10] perf,tools: Show STAT_READ in perf report kan.liang
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=20150820093028.GA4640@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox