Re: [v2.6.26] what's brewing in x86.git for v2.6.26

[Ingo Molnar <mingo@elte.hu>]

* Andrew Morton <akpm@linux-foundation.org> wrote:

> afaik the sysprof-vs-oprofile issue still hasn't been settled.  Maybe 
> it's no longer a relevant question with the new code - I just don't 
> know. Everything went all quiet and then this stuff happened.

i dont think there's any big issue here. Sysprof is a time and stack 
system-wide tracer/profiler, oprofile profiles CPU events - deep 
stacktracing is an afterthought there. And how do you set up oprofile to 
do precise time events?

with sysprof you can do:

  cd /sys/kernel/debug/tracing
  echo sysprof > current_tracer
  cat trace_pipe

and you'll see the trace events go by, live. The user-space bits of 
sysprof have been ported over to ftrace/sysprof already and it's a 
really nice tool that shows a deep stack-trace based hierarchical 
"vertical" profile instead of the usual finegrained profile.

It certainly helps that the author of the tracer plugin (Soeren 
Sandmann) is the author of the userspace app too - so there's a rather 
well-working feedback loop here ;-)

With oprofile all these things are rather indirect, the API is more 
complex, it forces per-CPU buffers, etc. etc. I think for 
instrumentation the driving force must be usability, and sysprof/ftrace 
is hands down more usable - to me at least.

	Ingo