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)
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
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
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
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
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
6 matches
Mail list logo