Re: [PATCH] tick/idle/powerpc: Do not register idle states with CPUIDLE_FLAG_TIMER_STOP set in periodic mode

2015-06-26 Thread Rafael J. Wysocki
On Thursday, June 25, 2015 09:05:49 AM Preeti U Murthy wrote: > On 06/25/2015 05:36 AM, Rafael J. Wysocki wrote: > > On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt > > wrote: > >> On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote: > >>> 4.2 material I suppose? > >> > >> And stab

Re: [PATCH] tick/idle/powerpc: Do not register idle states with CPUIDLE_FLAG_TIMER_STOP set in periodic mode

2015-06-24 Thread Preeti U Murthy
On 06/25/2015 05:36 AM, Rafael J. Wysocki wrote: > On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt > wrote: >> On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote: >>> 4.2 material I suppose? >> >> And stable. Without this, if you configure without TICK_ONESHOT, the >> machine will

Re: [PATCH] tick/idle/powerpc: Do not register idle states with CPUIDLE_FLAG_TIMER_STOP set in periodic mode

2015-06-24 Thread Benjamin Herrenschmidt
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote: > 4.2 material I suppose? And stable. Without this, if you configure without TICK_ONESHOT, the machine will hang. Cheers, Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org http

Re: [PATCH] tick/idle/powerpc: Do not register idle states with CPUIDLE_FLAG_TIMER_STOP set in periodic mode

2015-06-24 Thread Rafael J. Wysocki
On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt wrote: > On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote: >> 4.2 material I suppose? > > And stable. Without this, if you configure without TICK_ONESHOT, the > machine will hang. OK, which -stable? All of them or any specific se

Re: [PATCH] tick/idle/powerpc: Do not register idle states with CPUIDLE_FLAG_TIMER_STOP set in periodic mode

2015-06-24 Thread Rafael J. Wysocki
On Thu, Jun 25, 2015 at 12:10 AM, Michael Ellerman wrote: > > > On 24 June 2015 23:50:40 GMT+10:00, "Rafael J. Wysocki" > wrote: >>On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote: >>> On some archs, the local clockevent device stops in deep cpuidle >>states. >>> The broadcast frame

Re: [PATCH] tick/idle/powerpc: Do not register idle states with CPUIDLE_FLAG_TIMER_STOP set in periodic mode

2015-06-24 Thread Michael Ellerman
On 24 June 2015 23:50:40 GMT+10:00, "Rafael J. Wysocki" wrote: >On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote: >> On some archs, the local clockevent device stops in deep cpuidle >states. >> The broadcast framework is used to wakeup cpus in these idle states, >in >> which either

Re: [PATCH] tick/idle/powerpc: Do not register idle states with CPUIDLE_FLAG_TIMER_STOP set in periodic mode

2015-06-24 Thread Rafael J. Wysocki
On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote: > On some archs, the local clockevent device stops in deep cpuidle states. > The broadcast framework is used to wakeup cpus in these idle states, in > which either an external clockevent device is used to send wakeup ipis > or the hrtim

[PATCH] tick/idle/powerpc: Do not register idle states with CPUIDLE_FLAG_TIMER_STOP set in periodic mode

2015-06-23 Thread Preeti U Murthy
On some archs, the local clockevent device stops in deep cpuidle states. The broadcast framework is used to wakeup cpus in these idle states, in which either an external clockevent device is used to send wakeup ipis or the hrtimer broadcast framework kicks in in the absence of such a device. One cp