From: Li Shaohua <shaohua.li@intel.com>
To: lkml <linux-kernel@vger.kernel.org>,
ACPI-DEV <acpi-devel@lists.sourceforge.net>
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@suse.cz>
Subject: [RFC 0/6] S3 SMP support with physcial CPU hotplug
Date: Mon, 04 Apr 2005 10:05:42 +0800 [thread overview]
Message-ID: <1112580342.4194.329.camel@sli10-desk.sh.intel.com> (raw)
Hi,
The following 6 patches try to add suspend-to-ram (or S3) SMP support
for IA32. It's for support HT based system suspend/resume currently and
most of the code are also useful for physical CPU hotplug.
In a SMP system, after S3 resume, the BP is starting to execute the ACPI
wakeup address just like the UP case. And the APs possibly are in a
BIOS's busy loop. This just looks like the boot time case, we must use a
SIPI circle to wakeup the APs.
We uses the CPU hotplug infrastructure. In order to reuse the SMP boot
code, we clean up all CPU states after the CPU is dead, including its
idle thread, runqueue and other CPU states. Since the CPU is in idle
thread before suspend, we don't require to save and restore after resume
most of the CPU states.
Now the sequences of S3 are:
1. hotremove all APs, put them into idle thread.
2. follow UP S3 code path.
3. warm boot all APs.
4. UP all APs.
The patches are against 2.6.11-rc1 with Zwane's CPU hotplug patch in -mm
tree. To test the SMP S3, please don't enable MTRR driver (it's SMP
broken for Suspend/resume). And please kill syslogd, there is a bug in
the sususpend/resume refrigerator mechanism, which can be fixed by
swsusp2 refrigerator.
I'm looking forward to your comments. Thanks in advance!
Thanks,
Shaohua
next reply other threads:[~2005-04-04 2:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:05 Li Shaohua [this message]
2005-04-04 2:37 ` Andrew Morton
2005-04-04 2:42 ` Li Shaohua
2005-04-04 2:48 ` Andrew Morton
2005-04-04 2:49 ` Li Shaohua
2005-04-04 8:01 ` [ACPI] " Nigel Cunningham
2005-04-04 8:44 ` Li Shaohua
2005-04-04 9:10 ` Pavel Machek
2005-04-04 9:24 ` Li Shaohua
2005-04-04 9:32 ` Pavel Machek
2005-04-04 9:55 ` Nigel Cunningham
2005-04-04 8:44 ` Pavel Machek
2005-04-04 9:54 ` [ACPI] " Nigel Cunningham
2005-04-04 11:31 ` Pavel Machek
2005-04-04 11:46 ` Nigel Cunningham
2005-04-04 19:42 ` Zwane Mwaikambo
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=1112580342.4194.329.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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®