[lkml]   [2018]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH] MIPS: Oprofile: Drop support
Hi Robert,

On 04/05/18 11:26, Robert Richter wrote:
> On 04.05.18 10:54:32, Matt Redfearn wrote:
>> perf is available for MIPS and supports many more CPU types than oprofile.
>> oprofile userspace seemingly has been broken since 1.0.0 - removing oprofile
>> support from the MIPS kernel would not break it more thatn it already is,
> What do you mean with "oprofile is broken"? It looks like you modified
> Kconfig to enable oprofile and perf in parallel, which is not intended
> to work. Have you tried a kernel with oprofile disabled and perf
> enabled?

Oh I see what you mean - previously I was trying v1.1.0 of the userspace
with a kernel that has perf disabled - and that did not work (I assumed,
naively, that the kernel oprofile code was required to run the oprofile

Thanks for the pointer - I confirmed that oprofile 1.1.0 userspace tools
work with a kernel with "CONFIG_OPROFILE is not set", and

> As said, oprofile version 0.9.x is still available for cpus that do
> not support perf. What is the breakage?

The breakage I originally set out to fix was the MT support in perf.

Since the perf code shares so much copied code from oprofile, those same
issues exist in oprofile and ought to be addressed. But as newer
oprofile userspace does not use the (MIPS) kernel oprofile code, then we
could, perhaps, just remove it (as per the RFC). That would break legacy
tools (0.9.x) though...


> Thanks,
> -Robert

 \ /
  Last update: 2018-05-04 13:04    [W:0.050 / U:0.968 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site