From: Robert Hancock <hancockr@shaw.ca>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: CONFIG_HOTPLUG_CPU on x86
Date: Wed, 30 Jul 2008 13:29:00 -0600 [thread overview]
Message-ID: <4890C0FC.7010604@shaw.ca> (raw)
In-Reply-To: <fa.NXaOVSU/kxtRXoZokQC2Y0/po4M@ifi.uio.no>
Dimitri Sivanich wrote:
> I've heard folks say that hotplug cpu is very reliable. I'm assuming
> that's in the context of the x86 architecture. If so, how come
> CONFIG_HOTPLUG_CPU is still listed as EXPERIMENTAL in arch/x86/Kconfig?
> Should this be changed for the x86 architecture?
>
> config HOTPLUG_CPU
> bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
> depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
Yes, it's a bit bizarre that something needed for suspending almost any
current laptop is still marked as "experimental"..
next parent reply other threads:[~2008-07-30 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.NXaOVSU/kxtRXoZokQC2Y0/po4M@ifi.uio.no>
2008-07-30 19:29 ` Robert Hancock [this message]
2008-07-30 19:37 ` CONFIG_HOTPLUG_CPU on x86 Max Krasnyansky
2008-07-30 14:25 Dimitri Sivanich
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=4890C0FC.7010604@shaw.ca \
--to=hancockr@shaw.ca \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sivanich@sgi.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.