Re: [PATCH 0/26] oprofile: Performance counter multiplexing

[Andi Kleen <andi@firstfloor.org>]

Ingo Molnar <mingo@elte.hu> writes:
>
> As you note it below, in terms of development it's quite a 
> distraction to have active development in both facilities, when 
> oprofile is arguably on the to-be-obsoleted side of the equation. 

I don't see how it is distracting (for whom anyways?) at all to develop both.
It's just like two ethernet/SCSI/... drivers being developed in parallel
by different people. Happens all the time. The Linux development model
can handle it.

That said the biggest problem with oprofile right now that the
new buffer it's using is quite a lot less reliable and drops
events left and right on any non trivial load. That makes
oprofile very unreliable, especially in call graph mode.

So if there was a "legacy oprofile" it would be better to have
one that does not use the ring buffer, but using the old buffer which
at least worked. This would drop IBS support unfortunately,
but perhaps that could be just done in perf only (depends on 
how big the IBS user base for current oprofile is)

> And yes, AFAIK oprofile user-space is pretty much the only 
> user-space app that relies on the oprofile ABI - at least in the OSS 
> space. Robert, is there perhaps some bin-only oprofile based tool 
> that you implied before? Which one is it?

There are multiple, e.g. Zoom or the old HP tool whose name
escapes me now. Also I think there are a couple of minor forks around
in various distro trees.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.