Re: Not able to use HIGH_RES_TIMERS on ARM
From: Ajeet Yadav
Date: Thu Mar 22 2012 - 06:25:45 EST
I understand your point,
Our target (2.6) always had ARCH_USES_GETTIMEOFFSET=y , but still we
were able to use the TRACER in past until the patch "kill
GENERIC_TIMER" published, anyone will ask me remove this patch and use
TRACER, becaue it was working before. :)
If I set ARCH_USES_GETTIMEOFFSET=n to use this feature, my target
fail to boot. (reason I well understand from our past discussions)
but if do below, everything work find target as well as tracer.
--- linux-3.0.20/kernel/time/Kconfig 2012-02-06 23:01:45.000000000 +0530
+++ linux-3.0.20-dirty/kernel/time/Kconfig 2012-03-19
18:22:32.000000000 +0530
@@ -6,7 +6,7 @@ config TICK_ONESHOT
config NO_HZ
bool "Tickless System (Dynamic Ticks)"
- depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
+ depends on GENERIC_CLOCKEVENTS
select TICK_ONESHOT
help
This option enables a tickless system: timer interrupts will
@@ -15,7 +15,7 @@ config NO_HZ
config HIGH_RES_TIMERS
bool "High Resolution Timer Support"
- depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
+ depends on GENERIC_CLOCKEVENTS
select TICK_ONESHOT
help
This option enables high resolution timer support. If your
On Thu, Mar 22, 2012 at 3:32 PM, Russell King - ARM Linux
<linux@xxxxxxxxxxxxxxxx> wrote:
> On Thu, Mar 22, 2012 at 02:46:31PM +0530, Ajeet Yadav wrote:
>> Hi John,
>> On our target ÂARCH_USES_GETTIMEOFFSET=y, can you please help me how
>> can I useIRQSOFF_TRACER, PREEMPT_TRACER ?
>
> If you have ARCH_USES_GETTIMEOFFSET=y, the simple answer is: you can't.
>
> Your solution is to update your platform to use clock sources and clock
> events and disable the obsolete ARCH_USES_GETTIMEOFFSET option.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/