From: Pavel Machek <pavel@suse.cz>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Hugh Dickins <hugh@veritas.com>,
"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,
mingo@elte.hu
Subject: Re: [PATCH] stop on cpu lost
Date: Thu, 22 Jun 2006 23:44:14 +0200 [thread overview]
Message-ID: <20060622214414.GA4462@elf.ucw.cz> (raw)
In-Reply-To: <449AEF29.9070300@yahoo.com.au>
Hi!
> >remove infrastructure which would, for example, allow "ps" to show
> >such tasks. Perhaps such infrastructure should remain so long as
> >there are tasks there.
>
> They'll be in the global tasklist, so there should be no reason why
> they couldn't be migrated over to an online CPU with taskset. Shouldn't
> require any rewrites, IIRC.
>
> But after swsusp comes back up, it will be bringing up the same number
> of CPUs as went down, won't it? So you shouldn't get into that
> situation where you'd need to kill stuff, should you?
Well... unless something goes *very* wrong, we wake with same number
of CPUs. I've seen it fail in error cases (went to sleep with dual
cpus, but could not kick the second cpu to life during resume).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-06-22 21:45 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 [this message]
2006-06-22 19:52 ` Jeremy Fitzhardinge
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=20060622214414.GA4462@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=clameter@sgi.com \
--cc=hugh@veritas.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=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