Re: clock event device’s next_event

2017-10-24 Thread Sodagudi Prasad
On 2017-10-24 00:23, Thomas Gleixner wrote: On Mon, 23 Oct 2017, Sodagudi Prasad wrote: Hi Viresh and Thomas, In the functions tick_nohz_stop_sched_tick(), when expires = KTIME_MAX we are canceling the tick_sched_timer timer but we are not updating the clock event device’s next_event to

Re: clock event device’s next_event

2017-10-24 Thread Thomas Gleixner
On Mon, 23 Oct 2017, Sodagudi Prasad wrote: > Hi Viresh and Thomas, > > In the functions tick_nohz_stop_sched_tick(), when expires = KTIME_MAX we are > canceling the tick_sched_timer timer but we are not updating the clock event > device’s next_event to KTIME_MAX. > Due

clock event device’s next_event

2017-10-23 Thread Sodagudi Prasad
Hi Viresh and Thomas, In the functions tick_nohz_stop_sched_tick(), when expires = KTIME_MAX we are canceling the tick_sched_timer timer but we are not updating the clock event device’s next_event to KTIME_MAX. Due to that broadcast device’s next_event is not programmed properly and resulting