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

[Robert R. <rob...@am...>]

On 04.08.09 22:11:09, Ingo Molnar wrote:
> 
> * Arjan van de Ven <ar...@in...> wrote:
> 
> > On Mon, 3 Aug 2009 13:22:20 +0200
> > Ingo Molnar <mi...@el...> wrote:
> > > 
> > > This new oprofile multiplexing mechanism really overlaps the PMU 
> > > abstractions that perfcounters already provide, and i disagree 
> > > with this general direction. The code you wrote is clean though 
> > > so i've
> > 
> > is there any way that the oprofile interfaces can be written on 
> > top of the low level perf infrastructure?
> 
> Everything 'can' be done - the question is, is that the best 
> approach? The technically best interface to utilize perfcounters is 
> not to whack it into the oprofile kernel code, but to minimally 
> update the oprofile user-space code (the sample collection daemon) 
> to use the sys_perf_counter_open() system call.
> 
> It is by far the most elegant solution and needs no kernel changes 
> at all:
> 
> The oprofile daemon should open percpu sampling counters and create 
> oprofile-compatible sample files. That way the rest of the oprofile 
> user-space does not have to be touched at all. The raw event ids 
> that oprofile knows about can be used in perfcounter parameters 
> directly.
> 
> In such a mode of operation both oprofilefs and the dcookies syscall 
> can be omitted completely - all of the kernel side oprofile code 
> becomes mooted and pushed into legacy mode.
> 
> Is there any reason or oprofile property that makes this impossible 
> or undesirable to do?

The question is more if it makes sense. It's new to me dropping
user/kernel interfaces that are in use and forcing its developers to
rewrite their code. Oprofile is actively developed and in many
distros. It supports architectures perfcounters doesn't. So, what do
you want?

And why not having more than one profiling subsystem in the kernel? I
see also more than one type of car on the street though all of them
have 4 wheels.

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: rob...@am...