lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080811163111.GD4524@elte.hu>
Date:	Mon, 11 Aug 2008 18:31:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Dimitri Sivanich <sivanich@....com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Max Krasnyansky <maxk@...lcomm.com>
Subject: Re: [PATCH] x86: Remove EXPERIMENTAL restriction from
	CONFIG_HOTPLUG_CPU


* Dimitri Sivanich <sivanich@....com> wrote:

> This removes the EXPERIMENTAL restriction from CONFIG_HOTPLUG_CPU on 
> the x86 architecture.
>
> One question, should we default to 'Y'?

CONFIG_SUSPECT will select it anyway, and when suspend is disabled in 
all likelyhood it's an UP system that does not need any hotplug CPU 
support. So we dont want to enable it by default.

>  config HOTPLUG_CPU
> -	bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
> -	depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
> +	bool "Support for suspend on SMP and hot-pluggable CPUs"
> +	depends on SMP && HOTPLUG && !X86_VOYAGER
>  	---help---
> -	  Say Y here to experiment with turning CPUs off and on, and to
> -	  enable suspend on SMP systems. CPUs can be controlled through
> +	  Say Y here to allow turning CPUs off and on, and to enable
> +	  suspend on SMP systems. CPUs can be controlled through
>  	  /sys/devices/system/cpu.
>  	  Say N if you want to disable CPU hotplug and don't need to
>  	  suspend.

actually, the original text was incorrect/outdated, as HOTPLUG_CPU was 
already selected outside of EXPERIMENTAL, by PM_SLEEP_SMP.

So for all practical purposes HOTPLUG_CPU was already enabled in the 
Linux distro space by the side-effect of SUSPEND+PM_SLEEP enabling.

Where this change might matter is when CONFIG_PM is disabled 
intentionally on SMP - which is rather rare.

So i've clarified the text as per the commit below - is this fine with 
you?

	Ingo

------------------>
>From 7c13e6a3d15a4ebcc3f40df5f4d19665479f8ca3 Mon Sep 17 00:00:00 2001
From: Dimitri Sivanich <sivanich@....com>
Date: Mon, 11 Aug 2008 10:46:46 -0500
Subject: [PATCH] x86: remove EXPERIMENTAL restriction from CONFIG_HOTPLUG_CPU

This removes the EXPERIMENTAL restriction from CONFIG_HOTPLUG_CPU
on the x86 architecture.

Signed-off-by: Dimitri Sivanich <sivanich@....com>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
 arch/x86/Kconfig |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 3d0f2b6..7917962 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1371,14 +1371,14 @@ config PHYSICAL_ALIGN
 	  Don't change this unless you know what you are doing.
 
 config HOTPLUG_CPU
-	bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
-	depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
+	bool "Support for hot-pluggable CPUs"
+	depends on SMP && HOTPLUG && !X86_VOYAGER
 	---help---
-	  Say Y here to experiment with turning CPUs off and on, and to
-	  enable suspend on SMP systems. CPUs can be controlled through
-	  /sys/devices/system/cpu.
-	  Say N if you want to disable CPU hotplug and don't need to
-	  suspend.
+	  Say Y here to allow turning CPUs off and on. CPUs can be
+	  controlled through /sys/devices/system/cpu.
+	  ( Note: power management support will enable this option
+	    automatically on SMP systems. )
+	  Say N if you want to disable CPU hotplug.
 
 config COMPAT_VDSO
 	def_bool y
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ