On Thursday, August 02, 2012, Konrad Rzeszutek Wilk wrote:
> If the machine is booted without any cpu_idle driver set
> (b/c disable_cpuidle() has been called) we should follow
> other users of cpu_idle API and check the return value
> for NULL before using it.
> 
> Reported-by: Mark van Dijk <m...@internecto.net>
> Tested-by: Mark van Dijk <m...@internecto.net>
> Suggested-by: Jan Beulich <jbeul...@suse.com>
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.com>
> ---
>  drivers/idle/intel_idle.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
> index f559088..7383aa0 100644
> --- a/drivers/idle/intel_idle.c
> +++ b/drivers/idle/intel_idle.c
> @@ -607,7 +607,7 @@ static int __init intel_idle_init(void)
>       retval = cpuidle_register_driver(&intel_idle_driver);
>       if (retval) {

What about:

                struct cpuidle_driver *drv = cpuidle_get_driver();

                printk(KERN_DEBUG PREFIX "intel_idle yielding to %s",
                        drv ? drv->name : "none");

>               printk(KERN_DEBUG PREFIX "intel_idle yielding to %s",
> -                     cpuidle_get_driver()->name);
> +                     cpuidle_get_driver() ? cpuidle_get_driver()->name : 
> "none");
>               return retval;
>       }
>  
> 

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

Reply via email to