Re: [PATCH] tick/broadcast: set next event of bc to KTIME_MAX

Hi, This patch needs refine and I'll check more. Thanks a lot. On 2018年02月05日 10:17, kbuild test robot wrote: Hi Qiao, Thank you for the patch! Yet something to improve: [auto build test ERROR on tip/timers/nohz] [also build test ERROR on v4.15] [if your patch is applied to the wrong git

Re: [PATCH] tick/broadcast: set next event of bc to KTIME_MAX

Hi, This patch needs refine and I'll check more. Thanks a lot. On 2018年02月05日 10:17, kbuild test robot wrote: Hi Qiao, Thank you for the patch! Yet something to improve: [auto build test ERROR on tip/timers/nohz] [also build test ERROR on v4.15] [if your patch is applied to the wrong git

Re: [PATCH] tick/broadcast: set next event of bc to KTIME_MAX

Hi Qiao, Thank you for the patch! Yet something to improve: [auto build test ERROR on tip/timers/nohz] [also build test ERROR on v4.15] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] tick/broadcast: set next event of bc to KTIME_MAX

Hi Qiao, Thank you for the patch! Yet something to improve: [auto build test ERROR on tip/timers/nohz] [also build test ERROR on v4.15] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] tick/broadcast: set next event of bc to KTIME_MAX

In tick_handle_oneshot_broadcast, it doesn't reprogram tick-broadcast when no more event to set. In hardware it's true, but the next event value on broadcast device is expired, which will be used in idle broadcast enter. It may cause no more timer set in system in below case. nte_l:

[PATCH] tick/broadcast: set next event of bc to KTIME_MAX

In tick_handle_oneshot_broadcast, it doesn't reprogram tick-broadcast when no more event to set. In hardware it's true, but the next event value on broadcast device is expired, which will be used in idle broadcast enter. It may cause no more timer set in system in below case. nte_l: