All of lore.kernel.org
 help / color / mirror / Atom feed
* How to read the perf report output
@ 2015-04-17 10:52 Jack Wang
  2015-04-21 18:44 ` Daniel Speyer
  0 siblings, 1 reply; 2+ messages in thread
From: Jack Wang @ 2015-04-17 10:52 UTC (permalink / raw)
  To: linux-perf-users

Hello,

I'm tring to profile the system using perf, need help to under
standard the output better.

I'm running perf from linux-tools-3.16 from debian testing.

I use perf record -a -g -F 99 fio /dev/sdx to record a perf data, and
perf report -g show:

+   84.85%     0.11%         swapper  [kernel.kallsyms]   [k] cpu_startup_entry
+   84.17%     0.05%         swapper  [kernel.kallsyms]   [k] arch_cpu_idle
+   84.08%     0.06%         swapper  [kernel.kallsyms]   [k] cpuidle_idle_call
+   81.46%     0.00%         swapper  [kernel.kallsyms]   [k] start_secondary
+   75.25%     0.21%         swapper  [kernel.kallsyms]   [k]
cpuidle_enter_state
+   66.33%    66.29%         swapper  [kernel.kallsyms]   [k]
acpi_idle_enter_simple
+    9.60%     0.00%             fio  [kernel.kallsyms]   [k]
system_call_fastpath
+    7.74%     0.05%             fio  libaio.so.1.0.1     [.] io_submit
+    7.58%     0.00%             fio  [kernel.kallsyms]   [k] sys_io_submit
+    7.55%     0.05%             fio  [kernel.kallsyms]   [k] do_io_submit
+    7.38%     0.03%         swapper  [kernel.kallsyms]   [k] irq_exit
+    7.04%     0.02%             fio  [kernel.kallsyms]   [k] blkdev_aio_read
+    7.04%     0.15%         swapper  [kernel.kallsyms]   [k] __do_softirq
+    7.00%     0.03%             fio  [kernel.kallsyms]   [k]
generic_file_aio_read
+    6.96%     0.01%             fio  [kernel.kallsyms]   [k] blkdev_direct_IO
+    6.73%     0.53%             fio  [kernel.kallsyms]   [k]
__blockdev_direct_IO
+    6.09%     0.28%         swapper  [kernel.kallsyms]   [k]
call_function_single_interrupt
+    5.90%     0.01%         swapper  [kernel.kallsyms]   [k] acpi_idle_enter_c1
+    5.81%     0.01%         swapper  [kernel.kallsyms]   [k]
smp_call_function_single_interrupt
+    5.38%     0.13%         swapper  [kernel.kallsyms]   [k] scsi_softirq_done
+    5.31%     0.02%         swapper  [kernel.kallsyms]   [k] blk_done_softirq
+    5.22%     0.04%         swapper  [kernel.kallsyms]   [k]
scsi_finish_command


I know the first number is overhead percentage , but what's the second
one? it's looks new to me, anyone could give me a hint?

Thanks,

Regards,
Jack

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: How to read the perf report output
  2015-04-17 10:52 How to read the perf report output Jack Wang
@ 2015-04-21 18:44 ` Daniel Speyer
  0 siblings, 0 replies; 2+ messages in thread
From: Daniel Speyer @ 2015-04-21 18:44 UTC (permalink / raw)
  To: linux-perf-users

My copy of perf doesn't do that, but from looking at some stacks, I think
the first percentage is time spent in that function *including* children and
the second is *excluding*.  For example, cpu_startup_entry calls
arch_cpu_idle, and the latter accounts for most of the former's run time, so
they both have high inclusive time but the former has very low exclusive.

You might find things clearer using perf script instead of perf report.  It
doesn't analyze, but just dumps the results in an easy-to-read format
(intended to be the input to a script you would write, hence the name, but
you can also read it by hand).  You may need to specify a format.  I
generally use:

  sudo perf script -f trace:tid,comm,time,event,trace,sym,ip,dso

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-04-21 18:45 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-17 10:52 How to read the perf report output Jack Wang
2015-04-21 18:44 ` Daniel Speyer

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.