Does oprofile suffer from aliasing?

I'm looking for a way to determine what processes/threads are using up
the most CPU time on an ARM926 system.  We're running out of cycles
and want to know where to concentrate optimization efforts.  The
platform is currently running 2.6.22, but I could switch to a later
kernel if it would buy me some useful profiling data.

The values printed by 'top' are meaningless due to aliasing.  

Most of the relevent threads are triggered by timers on fixed cycles
and run for much less than one kernel tick. If I run a simple test
with a thread that does a some work every 10ms, and top is using 10ms
samples, then depending on the phase between the two 100Hz cycles, top
may think the thread is using 0% or 100% (or sometimes fairly random
values in between).

The documentation I've read on oprofile also refers to sampling,
though I can't find a description of how that sampling is done.  If
the sampling is random enough compared to the kernel timers, then it
might work.

Is oprofile going to produce useful data for the case where threads
are triggered on fixed cycles by timers?

If not, can anybody suggest anything else?

-- 
Grant Edwards               grant.b.edwards        Yow! Are you selling NYLON
                                  at               OIL WELLS??  If so, we can
                              gmail.com            use TWO DOZEN!!


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y