Re: [PATCH 19/21] clocksource: Improve comment explaining clocks_calc_max_nsecs()'s 50% safety margin

Peter Zijlstra
2015-04-02T19:04:54Z

On Thu, Apr 02, 2015 at 11:50:13AM -0700, John Stultz wrote:
>
> Right, but all of the time code relies on there being slack, since we
> can't be sure timers will not be slightly late.

Fair enough. My point is moot, I'll go crawl back into my cave ;-)