On Thu, Jan 19, 2017 at 4:23 PM, Hans Petter Selasky <hps_at_selasky.org> wrote: > > I can add prints/asserts to show that what happens is that > "state->nextcallopt > now" while "state->nextcall <= now". This situtation > is allowed to persist due to the way getnextcpuevent() is currently > implemented. > > Can the people CC'ed give the attached patch a spin and report back? > > As far as c2d system time is concerned, it works correctly for me w/ r312210. -Jia-Shiun.Received on Thu Jan 19 2017 - 09:35:25 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:09 UTC