From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@suse.cz>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
clameter@sgi.com, ntl@pobox.com, akpm@osdl.org,
linux-kernel@vger.kernel.org, ashok.raj@intel.com, ak@suse.de,
nickpiggin@yahoo.com.au, mingo@elte.hu
Subject: Re: [PATCH] stop on cpu lost
Date: Thu, 22 Jun 2006 12:52:32 -0700 [thread overview]
Message-ID: <449AF500.7000106@goop.org> (raw)
In-Reply-To: <20060622182231.GC4193@elf.ucw.cz>
Pavel Machek wrote:
> That's what I'd prefer... as swsusp uses cpu hotplug.
Does it have to? I presume this has been considered before, but what if
the other CPUs were just idled for suspend rather than "removed"? Or do
you actually need to simulate a hot-remove to make sure they get
suspended properly? In general, the "hot remove as suspend" thing seems
semantically awkward.
J
next prev parent reply other threads:[~2006-06-22 19:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 3:51 [PATCH] stop on cpu lost KAMEZAWA Hiroyuki
2006-06-22 5:56 ` Andrew Morton
2006-06-22 6:14 ` Christoph Lameter
2006-06-22 15:08 ` Nathan Lynch
2006-06-22 15:45 ` Randy.Dunlap
2006-06-22 15:45 ` Christoph Lameter
2006-06-22 16:05 ` KAMEZAWA Hiroyuki
2006-06-22 16:14 ` Christoph Lameter
2006-06-22 16:24 ` Randy.Dunlap
2006-06-22 17:04 ` Nathan Lynch
2006-06-22 17:20 ` KAMEZAWA Hiroyuki
2006-06-22 18:22 ` Pavel Machek
2006-06-22 18:35 ` Christoph Lameter
2006-06-22 18:37 ` Pavel Machek
2006-06-22 18:54 ` Hugh Dickins
2006-06-22 19:27 ` Nick Piggin
2006-06-22 19:46 ` Hugh Dickins
2006-06-22 19:57 ` Nick Piggin
2006-06-22 20:25 ` Hugh Dickins
2006-06-22 21:44 ` Pavel Machek
2006-06-22 19:52 ` Jeremy Fitzhardinge [this message]
2006-06-22 21:46 ` Pavel Machek
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=449AF500.7000106@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=ntl@pobox.com \
--cc=pavel@suse.cz \
--cc=rdunlap@xenotime.net \
/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