From: Pavel Machek <pavel@suse.cz>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Pavel Machek'" <pavel@suse.cz>,
Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>,
linux-kernel@vger.kernel.org,
large-discuss@lists.sourceforge.net,
Heiko Carstens <Heiko.Carstens@de.ibm.com>,
Jason McMullan <jmcmullan@linuxcare.com>,
Anton Blanchard <antonb@au1.ibm.com>,
Greg Kroah-Hartman <ghartman@us.ibm.com>,
rusty@rustcorp.com.au
Subject: Re: [ANNOUNCE] HotPlug CPU patch against 2.5.0
Date: Sat, 22 Dec 2001 17:05:52 +0100 [thread overview]
Message-ID: <20011222170552.C117@elf.ucw.cz> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C42D814@orsmsx111.jf.intel.com>
In-Reply-To: <59885C5E3098D511AD690002A5072D3C42D814@orsmsx111.jf.intel.com>
Hi!
> > From: Pavel Machek [mailto:pavel@suse.cz]
> > > This patch works on s390, s390x, x86 and ia64 architectures.
> > > It can also be applied against 2.4.16 with a little modification.
> > >
> > > Down CPU
> > > echo 0 > /proc/sys/kernel/cpu/<id>/online
> > >
> > > Up CPU
> > > echo 1 > /proc/sys/kernel/cpu/<id>/online
> >
> > Such patches are neccessary for ACPI S3/S4 sleep support. It
> > would be nice to
> > apply them soon.
>
> They are???
If you are going to S4 sleep, you should better make sure no other
processors are changing stuff under your hands. Easiest way to do that
is by putting them offline (I see no other good solutions). For S3
having to save state of one CPU is bad enough, having to save state of
8 would be bad, so putting them offline would be handy, too.
Pavel
--
"I do not steal MS software. It is not worth it."
-- Pavel Kankovsky
next prev parent reply other threads:[~2001-12-22 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 21:08 [ANNOUNCE] HotPlug CPU patch against 2.5.0 Grover, Andrew
2001-12-22 16:05 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-13 21:29 Kimio Suganuma
2001-12-13 22:44 ` Russell King
2001-12-14 0:20 ` Kimio Suganuma
2001-12-14 1:36 ` Dave Jones
2001-12-18 0:21 ` Pavel Machek
[not found] ` <Pine.LNX.4.33L2.0112181748040.20824-100000@dragon.pdx.osdl.net>
2001-12-20 0:17 ` Kimio Suganuma
2002-01-17 2:21 ` Randy.Dunlap
2002-01-17 7:28 ` Rusty Russell
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=20011222170552.C117@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=Heiko.Carstens@de.ibm.com \
--cc=andrew.grover@intel.com \
--cc=antonb@au1.ibm.com \
--cc=ghartman@us.ibm.com \
--cc=jmcmullan@linuxcare.com \
--cc=k-suganuma@mvj.biglobe.ne.jp \
--cc=large-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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