Re: [PATCH 3/3] clockevents: Switch state to ONESHOT_STOPPED for unused clockevent devices

2015-04-02 Thread Viresh Kumar
On 2 April 2015 at 19:07, Peter Zijlstra wrote: > Should we teach tick_program_event() about KTIME_MAX instead of adding > it to its callers? That's how I would have done, but Thomas (obviously for good reasons) rejected that :).. See reply to 2/3 for further details. -- To unsubscribe from this

Re: [PATCH 3/3] clockevents: Switch state to ONESHOT_STOPPED for unused clockevent devices

2015-04-02 Thread Peter Zijlstra
On Fri, Mar 27, 2015 at 10:44:29PM +0530, Viresh Kumar wrote: > kernel/time/hrtimer.c| 46 ++ > kernel/time/tick-sched.c | 3 +++ > 2 files changed, 45 insertions(+), 4 deletions(-) > > diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c >

Re: [PATCH 3/3] clockevents: Switch state to ONESHOT_STOPPED for unused clockevent devices

2015-04-02 Thread Peter Zijlstra
On Fri, Mar 27, 2015 at 10:44:29PM +0530, Viresh Kumar wrote: kernel/time/hrtimer.c| 46 ++ kernel/time/tick-sched.c | 3 +++ 2 files changed, 45 insertions(+), 4 deletions(-) diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c index

Re: [PATCH 3/3] clockevents: Switch state to ONESHOT_STOPPED for unused clockevent devices

2015-04-02 Thread Viresh Kumar
On 2 April 2015 at 19:07, Peter Zijlstra pet...@infradead.org wrote: Should we teach tick_program_event() about KTIME_MAX instead of adding it to its callers? That's how I would have done, but Thomas (obviously for good reasons) rejected that :).. See reply to 2/3 for further details. -- To

Re: [PATCH 3/3] clockevents: Switch state to ONESHOT_STOPPED for unused clockevent devices

2015-03-29 Thread Preeti U Murthy
On 03/27/2015 10:44 PM, Viresh Kumar wrote: > Clockevent device can now be stopped by switching to ONESHOT_STOPPED state, to > avoid getting spurious interrupts on a tickless CPU. > > Switch state to ONESHOT_STOPPED at following places: > > 1.) NOHZ_MODE_LOWRES Mode > > Timers & hrtimers are

Re: [PATCH 3/3] clockevents: Switch state to ONESHOT_STOPPED for unused clockevent devices

2015-03-29 Thread Preeti U Murthy
On 03/27/2015 10:44 PM, Viresh Kumar wrote: Clockevent device can now be stopped by switching to ONESHOT_STOPPED state, to avoid getting spurious interrupts on a tickless CPU. Switch state to ONESHOT_STOPPED at following places: 1.) NOHZ_MODE_LOWRES Mode Timers hrtimers are dependent

[PATCH 3/3] clockevents: Switch state to ONESHOT_STOPPED for unused clockevent devices

2015-03-27 Thread Viresh Kumar
Clockevent device can now be stopped by switching to ONESHOT_STOPPED state, to avoid getting spurious interrupts on a tickless CPU. Switch state to ONESHOT_STOPPED at following places: 1.) NOHZ_MODE_LOWRES Mode Timers & hrtimers are dependent on tick for their working in this mode and the only

[PATCH 3/3] clockevents: Switch state to ONESHOT_STOPPED for unused clockevent devices

2015-03-27 Thread Viresh Kumar
Clockevent device can now be stopped by switching to ONESHOT_STOPPED state, to avoid getting spurious interrupts on a tickless CPU. Switch state to ONESHOT_STOPPED at following places: 1.) NOHZ_MODE_LOWRES Mode Timers hrtimers are dependent on tick for their working in this mode and the only