Re: Removal of events for unsupported architectures or processor models

[Maynard J. <may...@us...>]

On 07/22/2014 03:27 PM, Aaro Koskinen wrote:
> Hi,
> 
> On Mon, Jul 21, 2014 at 06:08:16PM -0500, Maynard Johnson wrote:
>> As recently announced on the oprofile-list, OProfile release 1.0
>> will *NOT* include the legacy opcontrol-based profiler.
> 
> Maybe a stupid question, but does the new oprofile support anymore
> anything similar to "timer mode" profiling that was supported by
> the legacy oprofile driver? In some HW (e.g. OMAP) we have been unable
> to use performance counters due to HW bugs, but timer-based profiling
> has been still very useful.
Not a stupid question at all.  Right now, timer mode is supported only with the "legacy" opcontrol-based profiler.  The operf profiler could, theoretically, support a timer-like option (e.g., configuring perf_events with PERF_COUNT_SW_CPU_CLOCK).  I've not been motivated to add this myself, but would certainly review patches if anyone would like to contribute such support (after 1.0 is released).  But that may not help for your OMAP case anyway if perf_events is not supported at all for that processor type.

So, as I mentioned already, for those architectures or specific processor types that are not supported by perf_events, users should use opcontrol with oprofile release 0.9.9.

-Maynard
> 
> A.
>