Re: [RFC][PATCH v3] timekeeping: Cap adjustments so they don't exceed the maxadj value

2015-12-16 Thread Miroslav Lichvar
On Tue, Dec 15, 2015 at 09:48:06PM -0800, John Stultz wrote: > Thus its been occasionally noted that users have seen > confusing warnings like: > > Adjusting tsc more than 11% (5941981 vs 7759439) > v2: Catch single unit adjustment that was being made > repeatedly to push us past the

Re: [RFC][PATCH v3] timekeeping: Cap adjustments so they don't exceed the maxadj value

2015-12-16 Thread Miroslav Lichvar
On Tue, Dec 15, 2015 at 09:48:06PM -0800, John Stultz wrote: > Thus its been occasionally noted that users have seen > confusing warnings like: > > Adjusting tsc more than 11% (5941981 vs 7759439) > v2: Catch single unit adjustment that was being made > repeatedly to push us past the

[RFC][PATCH v3] timekeeping: Cap adjustments so they don't exceed the maxadj value

2015-12-15 Thread John Stultz
Thus its been occasionally noted that users have seen confusing warnings like: Adjusting tsc more than 11% (5941981 vs 7759439) We try to limit the maximum total adjustment to 11% (10% tick adjustment + 0.5% frequency adjustment). But this is done by bounding the requested adjustment values,

[RFC][PATCH v3] timekeeping: Cap adjustments so they don't exceed the maxadj value

2015-12-15 Thread John Stultz
Thus its been occasionally noted that users have seen confusing warnings like: Adjusting tsc more than 11% (5941981 vs 7759439) We try to limit the maximum total adjustment to 11% (10% tick adjustment + 0.5% frequency adjustment). But this is done by bounding the requested adjustment values,