[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130122215257.GU22517@atomide.com>
Date: Tue, 22 Jan 2013 13:52:57 -0800
From: Tony Lindgren <tony@...mide.com>
To: John Stultz <john.stultz@...aro.org>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Santosh Shilimkar <santosh.shilimkar@...com>,
Arnd Bergmann <arnd@...db.de>,
Peter Zijlstra <peterz@...radead.org>,
Matt Sealey <matt@...esi-usa.com>,
LKML <linux-kernel@...r.kernel.org>,
Ben Dooks <ben@...tec.co.uk>, Ingo Molnar <mingo@...hat.com>,
Linux ARM Kernel ML <linux-arm-kernel@...ts.infradead.org>
Subject: Re: One of these things (CONFIG_HZ) is not like the others..
* John Stultz <john.stultz@...aro.org> [130122 11:02]:
>
> Correct, with HRT, we actually trigger the HZ-frequency timer tick
> from an hrtimer (which expires based on the system time driven by
> the clocksource). Thus even if there is a theoretical error between
> the ideal HZ and what the hardware can do, that error will not
> propagate forward.
If there's no cumulative error, sounds like the way to go is to select
HRT for ARM multiplatform builds and set the HZ to 100 then.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists