On Thu, Mar 2, 2017 at 1:02 AM, David Engraf <[email protected]> wrote: > The scheduler clock framework may not use the correct timeout for the clock > wrap. This happens when a new clock driver calls sched_clock_register() > after the kernel called sched_clock_postinit(). In this case the clock wrap > timeout is too long thus sched_clock_poll() is called too late and the clock > already wrapped. > > On my ARM system the scheduler was no longer scheduling any other task than > the idle task because the sched_clock() wrapped. > > Signed-off-by: David Engraf <[email protected]>
Thanks for sending this in! It looks sane, so I've queued it. thanks -john
