From: Dimitri Sivanich <sivanich@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Cc: Max Krasnyansky <maxk@qualcomm.com>
Subject: [PATCH] x86: Remove EXPERIMENTAL restriction from CONFIG_HOTPLUG_CPU
Date: Mon, 11 Aug 2008 10:46:46 -0500 [thread overview]
Message-ID: <20080811154646.GB8181@sgi.com> (raw)
This removes the EXPERIMENTAL restriction from CONFIG_HOTPLUG_CPU on the x86 architecture.
One question, should we default to 'Y'?
Signed-off-by: Dimitri Sivanich <sivanich@sgi.com>
Index: linux/arch/x86/Kconfig
===================================================================
--- linux.orig/arch/x86/Kconfig 2008-07-30 14:45:16.000000000 -0500
+++ linux/arch/x86/Kconfig 2008-07-30 14:47:54.000000000 -0500
@@ -1365,11 +1365,11 @@ 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 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.
next reply other threads:[~2008-08-11 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 15:46 Dimitri Sivanich [this message]
2008-08-11 16:31 ` [PATCH] x86: Remove EXPERIMENTAL restriction from CONFIG_HOTPLUG_CPU Ingo Molnar
2008-08-11 16:34 ` Dimitri Sivanich
2008-08-13 7:34 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-07-30 19:58 Dimitri Sivanich
2008-08-04 17:55 ` Max Krasnyansky
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=20080811154646.GB8181@sgi.com \
--to=sivanich@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
/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.