On Sun, May 26, 2013 at 05:35:42PM -0400, [email protected] wrote: > From: KOSAKI Motohiro <[email protected]> > > Currently glibc rt/tst-cpuclock2 test(*) sporadically fails because > scheduler delta can be accounted twice from thread_group_cputimer() > and account_group_exec_runtime(). > > Finally, clock_nanosleep() wakes up earlier than an argument. This is posix > violation. This issue was introduced by commit d670ec1317 (posix-cpu-timers: > Cure SMP wobbles). > > (*) > http://sourceware.org/git/?p=glibc.git;a=blob;f=rt/tst-cpuclock2.c;h=6752721717f959e89c0d692b3f1ee082d507eec2;hb=HEAD > > Cc: Olivier Langlois <[email protected]> > Cc: Thomas Gleixner <[email protected]>
So with this patch the timer sample can be (nr_threads * TICK_NSEC) nsecs behind the clock in the worst case. This is still better than possibly (nr_threads * TICK_NSEC) nsecs ahead of the clock in the worst case like we have before the patch :) But the worst case can be unbounded with full dynticks tasks. May be the ideal thing would be to perform an update_curr() on the threads before we read their sum_exec_runtime, This way we make sure we are never far away behind. This needs to be done on top of your change anyway because we still want to avoid the double count, so: Acked-by: Frederic Weisbecker <[email protected]> Thanks. -- 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/
