Re: [PATCH 1/3] clockevents: Introduce CLOCK_EVT_STATE_ONESHOT_STOPPED state

2015-04-06 Thread Kevin Hilman
Viresh Kumar writes: > When no timers/hrtimers are pending, the expiry time is set to a special > value: > 'KTIME_MAX'. This normally happens with NO_HZ_{IDLE|FULL} in both > LOWRES/HIGHRES > modes. > > When 'expiry == KTIME_MAX', we either cancel the 'tick-sched' hrtimer > (NOHZ_MODE_HIGHRES)

Re: [PATCH 1/3] clockevents: Introduce CLOCK_EVT_STATE_ONESHOT_STOPPED state

2015-04-06 Thread Kevin Hilman
Viresh Kumar viresh.ku...@linaro.org writes: When no timers/hrtimers are pending, the expiry time is set to a special value: 'KTIME_MAX'. This normally happens with NO_HZ_{IDLE|FULL} in both LOWRES/HIGHRES modes. When 'expiry == KTIME_MAX', we either cancel the 'tick-sched' hrtimer

Re: [PATCH 1/3] clockevents: Introduce CLOCK_EVT_STATE_ONESHOT_STOPPED state

2015-03-29 Thread Preeti U Murthy
On 03/27/2015 10:44 PM, Viresh Kumar wrote: > When no timers/hrtimers are pending, the expiry time is set to a special > value: > 'KTIME_MAX'. This normally happens with NO_HZ_{IDLE|FULL} in both > LOWRES/HIGHRES > modes. > > When 'expiry == KTIME_MAX', we either cancel the 'tick-sched' hrtimer

Re: [PATCH 1/3] clockevents: Introduce CLOCK_EVT_STATE_ONESHOT_STOPPED state

2015-03-29 Thread Preeti U Murthy
On 03/27/2015 10:44 PM, Viresh Kumar wrote: When no timers/hrtimers are pending, the expiry time is set to a special value: 'KTIME_MAX'. This normally happens with NO_HZ_{IDLE|FULL} in both LOWRES/HIGHRES modes. When 'expiry == KTIME_MAX', we either cancel the 'tick-sched' hrtimer

[PATCH 1/3] clockevents: Introduce CLOCK_EVT_STATE_ONESHOT_STOPPED state

2015-03-27 Thread Viresh Kumar
When no timers/hrtimers are pending, the expiry time is set to a special value: 'KTIME_MAX'. This normally happens with NO_HZ_{IDLE|FULL} in both LOWRES/HIGHRES modes. When 'expiry == KTIME_MAX', we either cancel the 'tick-sched' hrtimer (NOHZ_MODE_HIGHRES) or skip reprogramming clockevent device

[PATCH 1/3] clockevents: Introduce CLOCK_EVT_STATE_ONESHOT_STOPPED state

2015-03-27 Thread Viresh Kumar
When no timers/hrtimers are pending, the expiry time is set to a special value: 'KTIME_MAX'. This normally happens with NO_HZ_{IDLE|FULL} in both LOWRES/HIGHRES modes. When 'expiry == KTIME_MAX', we either cancel the 'tick-sched' hrtimer (NOHZ_MODE_HIGHRES) or skip reprogramming clockevent device