On Thu, Nov 14, 2013 at 03:50:40PM +0100, Miroslav Lichvar wrote: > include/linux/timekeeper_internal.h | 4 + > kernel/time/timekeeping.c | 209 > +++++------------------------------- > 2 files changed, 31 insertions(+), 182 deletions(-)
This looks like an impressive simplification... > - * So the following can be confusing. Yep. So I really have no idea how the deleted code worked (or didn't work for nohz), but I can confirm that nohz time keeping is broken under light system load. Running a high load (like recompiling the kernel on all cores for CONFIG_HZ_PERIODIC=y ;) hides the issue, but that is obviously not the right solution. Out of my ignorance, two questions spring to mind. 1. Considering the simplicity of Miroslav's patch, what was the benefit of the much more complicated code in the first place? 2. Does this patch work in the CONFIG_HZ_PERIODIC case just as well as the deleted code? Thanks, Richard -- 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/
