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 -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
