All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-pm@vger.kernel.org, patches@linaro.org,
	linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] cpuidle: improve governor Kconfig options
Date: Tue, 28 May 2013 13:46:58 +0200	[thread overview]
Message-ID: <1578834.dvFIpyCvrt@vostro.rjw.lan> (raw)
In-Reply-To: <1369688458-9114-1-git-send-email-daniel.lezcano@linaro.org>

On Monday, May 27, 2013 11:00:58 PM Daniel Lezcano wrote:
> Each governor is suitable for different kernel configurations: the menu
> governor suits better for a tickless system, while the ladder governor fits
> better for a periodic timer tick system.
> 
> The Kconfig does not allow to [un]select a governor, thus both are compiled in
> the kernel but the init order makes the menu governor to be the last one to be
> registered, so becoming the default. The only way to switch back to the ladder
> governor is to enable the sysfs governor switch in the kernel command line.
> 
> Because it seems nobody complained about this, the menu governor is used by
> default most of the time on the system, having both governors is not really
> necessary on a tickless system but there isn't a config option to disable one
> or another governor.
> 
> Create a submenu for cpuidle and add a label for each governor, so we can see
> the option in the menu config and enable/disable it.
> 
> The governors will be enabled depending on the CONFIG_NO_HZ option:
>  - If CONFIG_NO_HZ is set, then the menu governor is selected and the ladder
>    governor is optional, defaulting to 'no'

Why not defaulting to 'yes'?  That'd be backwards compatible, wouldn't it?

>  - If CONFIG_NO_HZ is not set, then the ladder governor is selected and the
>    menu governor is optional, defaulting to 'no'

Are you sure this is not going to introduce regressions with CONFIG_NO_HZ
unset?

Rafael


> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
>  drivers/cpuidle/Kconfig |   20 +++++++++-----------
>  1 file changed, 9 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/cpuidle/Kconfig b/drivers/cpuidle/Kconfig
> index c4cc27e..90c2f39 100644
> --- a/drivers/cpuidle/Kconfig
> +++ b/drivers/cpuidle/Kconfig
> @@ -1,7 +1,9 @@
>  
> -config CPU_IDLE
> +menuconfig CPU_IDLE
>  	bool "CPU idle PM support"
>  	default y if ACPI || PPC_PSERIES
> +	select CPU_IDLE_GOV_LADDER if (!NO_HZ && !NO_HZ_IDLE)
> +	select CPU_IDLE_GOV_MENU if (NO_HZ || NO_HZ_IDLE)
>  	help
>  	  CPU idle is a generic framework for supporting software-controlled
>  	  idle processor power management.  It includes modular cross-platform
> @@ -9,9 +11,10 @@ config CPU_IDLE
>  
>  	  If you're using an ACPI-enabled platform, you should say Y here.
>  
> +if CPU_IDLE
> +
>  config CPU_IDLE_MULTIPLE_DRIVERS
>          bool "Support multiple cpuidle drivers"
> -        depends on CPU_IDLE
>          default n
>          help
>           Allows the cpuidle framework to use different drivers for each CPU.
> @@ -19,24 +22,19 @@ config CPU_IDLE_MULTIPLE_DRIVERS
>           states. If unsure say N.
>  
>  config CPU_IDLE_GOV_LADDER
> -	bool
> -	depends on CPU_IDLE
> -	default y
> +	bool "Ladder governor (for periodic timer tick)"
> +	default n if (NO_HZ || NO_HZ_IDLE)
>  
>  config CPU_IDLE_GOV_MENU
> -	bool
> -	depends on CPU_IDLE && NO_HZ
> -	default y
> +	bool "Menu governor (for tickless system)"
> +	default n if (!NO_HZ && !NO_HZ_IDLE)
>  
>  config ARCH_NEEDS_CPU_IDLE_COUPLED
>  	def_bool n
>  
> -if CPU_IDLE
> -
>  config CPU_IDLE_CALXEDA
>  	bool "CPU Idle Driver for Calxeda processors"
>  	depends on ARCH_HIGHBANK
>  	help
>  	  Select this to enable cpuidle on Calxeda processors.
> -
>  endif
> 
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-05-28 11:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 21:00 [PATCH] cpuidle: improve governor Kconfig options Daniel Lezcano
2013-05-28 11:46 ` Rafael J. Wysocki [this message]
2013-05-28 12:23   ` Daniel Lezcano
2013-05-28 12:23     ` Daniel Lezcano
2013-05-28 12:42     ` Rafael J. Wysocki
2013-05-28 12:42       ` Rafael J. Wysocki
2013-05-28 13:23       ` Daniel Lezcano
2013-05-28 13:23         ` Daniel Lezcano
2013-05-28 21:26         ` Rafael J. Wysocki
2013-05-28 21:26           ` Rafael J. Wysocki
2013-05-28 21:39           ` Daniel Lezcano
2013-05-28 21:39             ` Daniel Lezcano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1578834.dvFIpyCvrt@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=daniel.lezcano@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.