On 01/09/2015 04:34 PM, John Stultz wrote: > The clocksource logic has a number of places where we try to > include a safety margin. Most of these are 12% safety margins, > but they are inconsistently applied and sometimes are applied > on top of each other. > > Additionally, in the previous patch, we corrected an issue > where we unintentionally in effect created a 50% saftey margin, > which these 12.5% margins where then added to. > > So to siplify the logic here, this patch removes the various > 12.5% margins, and consolidates adding the margin in one place: > clocks_calc_max_nsecs(). > > Addtionally, Linus prefers a 50% safety margin, as it allows > bad clock values to be more easily caught. This should really > have no net effect, due to the corrected issue earlier which > caused greater then 50% margins to be used w/o issue. > > Cc: Dave Jones <[email protected]> > Cc: Linus Torvalds <[email protected]> > Cc: Thomas Gleixner <[email protected]> > Cc: Richard Cochran <[email protected]> > Cc: Prarit Bhargava <[email protected]> > Cc: Stephen Boyd <[email protected]> > Cc: Ingo Molnar <[email protected]> > Cc: Peter Zijlstra <[email protected]> > Signed-off-by: John Stultz <[email protected]> > ---
For sched_clock.c part Acked-by: Stephen Boyd <[email protected]> -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
