[RFC PATCH v4 1/4] cpuidle: Add time keeping and irq enabling

[Colin Cross]

On Tue, Jan 31, 2012 at 7:00 PM, Robert Lee <rob.lee at linaro.org> wrote:
> Make necessary changes to add implement time keepign and irq enabling
keeping
> in the core cpuidle code.  This will allow the remove of these
> functionalities from the platform cpuidle implementations.
>
> Signed-off-by: Robert Lee <rob.lee at linaro.org>
> ---
>  drivers/cpuidle/cpuidle.c |   75 +++++++++++++++++++++++++++++++++++---------
>  include/linux/cpuidle.h   |   26 ++++++++++-----
>  2 files changed, 76 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
> index 59f4261..8ea0fc3 100644
> --- a/drivers/cpuidle/cpuidle.c
> +++ b/drivers/cpuidle/cpuidle.c
> @@ -57,14 +57,18 @@ static int __cpuidle_register_device(struct cpuidle_device *dev);
>  * cpuidle_idle_call - the main idle loop
>  *
>  * NOTE: no locks or semaphores should be used here
> + * NOTE: Should only be called from a local irq disabled context
>  * return non-zero on failure
> + *
>  */
>  int cpuidle_idle_call(void)
>  {
>        struct cpuidle_device *dev = __this_cpu_read(cpuidle_devices);
>        struct cpuidle_driver *drv = cpuidle_get_driver();
>        struct cpuidle_state *target_state;
> -       int next_state, entered_state;
> +       int idx, ret = 0;
> +       ktime_t t1, t2;
> +       s64 diff;
>
>        if (off)
>                return -ENODEV;
> @@ -86,37 +90,76 @@ int cpuidle_idle_call(void)
>  #endif
>
>        /* ask the governor for the next state */
> -       next_state = cpuidle_curr_governor->select(drv, dev);
> +       idx = cpuidle_curr_governor->select(drv, dev);
> +
> +       target_state = &drv->states[idx];
> +
> +       /*
> +        * Check with the device to see if it can enter this state or if another
> +        * state should be used.
> +        */
> +       if (target_state->pre_enter) {
> +               idx = target_state->
> +                       pre_enter(dev, drv, idx);
Unnecessary line wrap and braces.

What's the point of the pre_enter call?  This seems very similar to
the prepare call that was removed in 3.2.  Drivers can already demote
the target state in their enter call.  The only thing you do between
pre_enter and enter is trace and account for the time.  Is there some
long call you don't want included in the idle time?  Some
documentation would help, and you need to very clearly define the
semantics of when post_enter gets called when pre_enter or enter
return errors.