From: Pavel Machek <pavel@ucw.cz>
To: Li Shaohua <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
ACPI-DEV <acpi-devel@lists.sourceforge.net>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
Len Brown <len.brown@intel.com>
Subject: Re: [RFC 4/6]Add kconfig for S3 SMP
Date: Mon, 4 Apr 2005 10:59:32 +0200 [thread overview]
Message-ID: <20050404085932.GE14642@elf.ucw.cz> (raw)
In-Reply-To: <1112580364.4194.342.camel@sli10-desk.sh.intel.com>
Hi!
> Add kconfig for IA32 S3 SMP.
>
> Thanks,
> Shaohua
>
> ---
>
> linux-2.6.11-root/kernel/power/Kconfig | 7 +++++++
> 1 files changed, 7 insertions(+)
>
> diff -puN kernel/power/Kconfig~smp_s3_kconfig kernel/power/Kconfig
> --- linux-2.6.11/kernel/power/Kconfig~smp_s3_kconfig 2005-03-31 10:49:57.156487160 +0800
> +++ linux-2.6.11-root/kernel/power/Kconfig 2005-03-31 10:49:57.158486856 +0800
> @@ -72,3 +72,10 @@ config PM_STD_PARTITION
> suspended image to. It will simply pick the first available swap
> device.
>
> +config STR_SMP
> + bool "Suspend to RAM SMP support (EXPERIMENTAL)"
> + depends on EXPERIMENTAL && ACPI_SLEEP && !X86_64
> + depends on HOTPLUG_CPU
> + default y
> + ---help---
> + enable Suspend to RAM SMP support. Some HT systems require this.
Should this be config option? If we have ACPI_SLEEP and SMP set, we
should probably require this one (so that user does not have to
care).... Also name is "interesting", perhaps CONFIG_SMP_SLEEP or
something?
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-04-04 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:06 Li Shaohua
2005-04-04 8:59 ` Pavel Machek [this message]
2005-04-04 9:14 ` Li Shaohua
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=20050404085932.GE14642@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=zwane@linuxpower.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®