On Thu, Mar 2, 2017 at 1:02 AM, David Engraf 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
On Thu, Mar 2, 2017 at 1:02 AM, David Engraf 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
2 matches
Mail list logo