On Sun, Jan 11, 2015 at 3:41 AM, Richard Cochran <richardcoch...@gmail.com> wrote: > On Fri, Jan 09, 2015 at 04:34:18PM -0800, John Stultz wrote: >> So this series is the result of earlier discussions with Linus >> and his suggestions around improvements to clocksource validation >> in the hope we can more easily catch bad hardware. > > Why penalize most users just because of a random hardware failure? > Why not make the "catching code" a compile time option?
Yea, I've not looked at the actual performance impact yet, but things like the read-time capping (which is in the hot path) could be put under a debug config. Thanks for the suggestion! -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
