Re: [PATCH RFC 03/10] perf,tools: support option --socket

From: Jiri Olsa
Date: Thu Aug 20 2015 - 05:30:53 EST


On Tue, Aug 18, 2015 at 05:25:39AM -0400, kan.liang@xxxxxxxxx wrote:
> From: Kan Liang <kan.liang@xxxxxxxxx>
>
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/