lkml.org 
[lkml]   [2009]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: How to use a different sched_clock() for ftrace on omap?
Kevin Hilman wrote:
> Tim Bird <tim.bird@am.sony.com> writes:
>
>> Hi all,
>>
>> I've worked up a replacement sched_clock for ftrace on my omap platform.
>> The current sched_clock, based on the 32K timer, has low resolution and
>> doesn't provide very useful results.
>>
>> Unfortunately, I'm not sure the best way to use my special one, in place
>> of a common one in arch/arm/plat-omap/common.c
>
> Hi Tim,
>
> If you're comiling mach-omap1/time.c than you've enabled the
> higher-resolution MPU timer with CONFIG_OMAP_MPU_TIMER, right?

Yes.

> In that case, you could make the one in plat-omap/common.c inside and
> #ifndef CONFIG_OMAP_MPU_TIMER and put the new one in the MPU_TIMER
> code.
>
> To be complete, you should add the same to the mach-omap2/timer-gp.c
> as well.

I was trying to avoid using #ifdefs, but maybe in this case it
makes sense. There are tradeoffs in using the different timers
(nicely described in plat-omap/Kconfig help entries), so IMHO it
would be good to make this a config preference.

I'll work up a patch in this style and send it along.
-- Tim


=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================



\
 
 \ /
  Last update: 2009-05-07 19:23    [W:0.047 / U:0.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site