On Tue, Aug 30, 2011 at 10:53 AM, Turgis, Frederic f-turgis@ti.com wrote:
Hi,
As indicated by Siamashka, we are expected to operate at scheduler tick rate, i.e. 128Hz (drivers/oprofile/timer_int.c). From your test, we have 84 ticks, i.e. 656ms of test. Is that correct ? I checked that also in our Android kernel and it was the same.
Makes sense, but it brings me back to my earlier lament, that a user tunable option to up the rate for the purpose of collecting more samples would be quite desirable.
The only impacts we have seen in the past are related to idle time. For same duration, we had less ticks if more idle time. But Android guys, who used it more than us, never really complained on this or timer granularity. Probably this was more orented to multimedia use cases so 10s of s.
Regards Fred
Frederic Turgis OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920