Hi Frederic,
[auto build test ERROR on tip/timers/core]
[cannot apply to v4.10-rc8 next-20170216]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Frederic-Weisbecker/nohz-Fix-possible-missing-clo
Hi Frederic,
[auto build test ERROR on tip/timers/core]
[cannot apply to v4.10-rc8 next-20170216]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Frederic-Weisbecker/nohz-Fix-possible-missing-clo
2017-02-08 0:44 GMT+08:00 Frederic Weisbecker :
> ts->next_tick keeps track of the next tick deadline in order to optimize
> clock programmation on irq exit and avoid redundant clock device writes.
>
> Now if ts->next_tick missed an update, we may spuriously miss a clock
> reprog later as the nohz
On Tue, 2017-02-07 at 17:44 +0100, Frederic Weisbecker wrote:
> ts->next_tick keeps track of the next tick deadline in order to
> optimize
> clock programmation on irq exit and avoid redundant clock device
> writes.
>
> Now if ts->next_tick missed an update, we may spuriously miss a clock
> reprog
ts->next_tick keeps track of the next tick deadline in order to optimize
clock programmation on irq exit and avoid redundant clock device writes.
Now if ts->next_tick missed an update, we may spuriously miss a clock
reprog later as the nohz code is fooled by an obsolete next_tick value.
This is w
5 matches
Mail list logo
