Re: [PATCH 0/3] cpuidle: updates related to tick_broadcast_enter() failures

[Daniel Lezcano]

On 05/10/2015 01:15 AM, Rafael J. Wysocki wrote:
> On Saturday, May 09, 2015 10:33:05 PM Rafael J. Wysocki wrote:
> > On Saturday, May 09, 2015 10:11:41 PM Rafael J. Wysocki wrote:
> > > On Saturday, May 09, 2015 11:19:16 AM Preeti U Murthy wrote:
> > > > Hi Rafael,
> > > >
> > > > On 05/08/2015 07:48 PM, Rafael J. Wysocki wrote:
> > >
> > > [cut]
> > >
> > > > > > +	/* Take note of the planned idle state. */
> > > > > > +	idle_set_state(smp_processor_id(), target_state);
> > > > >
> > > > > And I wouldn't do this either.
> > > > >
> > > > > The behavior here is pretty much as though the driver demoted the state chosen
> > > > > by the governor and we don't call idle_set_state() again in those cases.
> > > >
> > > > Why is this wrong?
> > >
> > > It is not "wrong", but incomplete, because demotions done by the cpuidle driver
> > > should also be taken into account in the same way.
> > >
> > > But I'm seeing that the recent patch of mine that made cpuidle_enter_state()
> > > call default_idle_call() was a mistake, because it might confuse find_idlest_cpu()
> > > significantly as to what state the CPU is in.  I'll drop that one for now.
> >
> > OK, done.
> >
> > So after I've dropped it I think we need to do three things:
> > (1) Move the idle_set_state() calls to cpuidle_enter_state().
> > (2) Make cpuidle_enter_state() call default_idle_call() again, but this time
> >      do that *before* it has called idle_set_state() for target_state.
> > (3) Introduce demotion as per my last patch.
> >
> > Let me cut patches for that.
>
> Done as per the above and the patches follow in replies to this messge.
>
> All on top of the current linux-next branch of the linux-pm.git tree.

IMO the resulting code is more and more confusing.

Except I miss something, the tick_broadcast_enter can fail only if the 
local timer of the current cpu is used as a broadcast timer (which is 
the case today for PPC only).

The correct fix would be to tie this local timer with the cpu power 
domain and disable the idle state powering down this domain like it was 
done for the renesas cpuidle driver.

IOW, the cpu power domain is in use (because of its local timer), so we 
shouldn't shut it down.

No ?

I am aware this is not easily fixable because the genpd framework is 
incomplete and has some restrictions but I believe it is worth to have a 
discussion. Add Kevin and Ulf in Cc.

  -- Daniel

--
 <http://www.linaro.org/> Linaro.org â Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/