From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Cedric Le Goater <clg@fr.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
jeremy@goop.org, arnd@arndb.de,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrey Mirkin <major@openvz.org>
Subject: Re: [RFC v6][PATCH 0/9] Kernel based checkpoint/restart
Date: Mon, 13 Oct 2008 09:43:43 -0700 [thread overview]
Message-ID: <1223916223.29877.14.camel@nimitz> (raw)
In-Reply-To: <48F30315.1070909@fr.ibm.com>
On Mon, 2008-10-13 at 10:13 +0200, Cedric Le Goater wrote:
> hmm, that's rather complex, because we have to take into account the
> kernel stack, no ? This is what Andrey was trying to solve in his patchset
> back in September :
>
> http://lkml.org/lkml/2008/9/3/96
>
> the restart phase simulates a clone and switch_to to (not) restore the kernel
> stack. right ?
Do we ever have to worry about the kernel stack if we simply say that
tasks have to be *in* userspace when we checkpoint them. If a task is
in an uninterruptable wait state, I'm not sure it's safe to checkpoint
it anyway.
-- Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-10-13 16:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 10:19 Oren Laadan
2008-10-08 10:19 ` [RFC v6][PATCH 1/9] Create syscalls: sys_checkpoint, sys_restart Oren Laadan
2008-10-08 10:19 ` [RFC v6][PATCH 2/9] General infrastructure for checkpoint restart Oren Laadan
2008-10-08 10:19 ` [RFC v6][PATCH 3/9] x86 support for checkpoint/restart Oren Laadan
2008-10-10 10:21 ` Cedric Le Goater
2008-10-10 10:24 ` Oren Laadan
2008-10-08 10:19 ` [RFC v6][PATCH 4/9] Dump memory address space Oren Laadan
2008-10-08 10:19 ` [RFC v6][PATCH 5/9] Restore " Oren Laadan
2008-10-08 15:35 ` Dave Hansen
2008-10-08 10:19 ` [RFC v6][PATCH 6/9] Checkpoint/restart: initial documentation Oren Laadan
2008-10-08 10:19 ` [RFC v6][PATCH 7/9] Infrastructure for shared objects Oren Laadan
2008-10-08 10:19 ` [RFC v6][PATCH 8/9] Dump open file descriptors Oren Laadan
2008-10-08 10:19 ` [RFC v6][PATCH 9/9] Restore open file descriprtors Oren Laadan
2008-10-09 12:46 ` [RFC v6][PATCH 0/9] Kernel based checkpoint/restart Ingo Molnar
2008-10-09 12:58 ` Dave Hansen
2008-10-09 13:17 ` Ingo Molnar
2008-10-09 13:34 ` Dave Hansen
2008-10-09 13:44 ` Ingo Molnar
2008-10-09 16:50 ` Dave Hansen
2008-10-10 15:39 ` Ingo Molnar
2008-10-13 8:13 ` Cedric Le Goater
2008-10-13 16:12 ` Oren Laadan
2008-10-15 15:13 ` Cedric Le Goater
2008-10-15 23:59 ` Oren Laadan
2008-10-13 16:43 ` Dave Hansen [this message]
2008-10-15 15:15 ` Cedric Le Goater
2008-10-16 0:06 ` Oren Laadan
2008-10-16 12:35 ` Daniel Lezcano
2008-10-16 13:49 ` Oren Laadan
2008-10-16 22:51 ` Peter Chubb
2008-10-17 6:30 ` David Newall
2008-10-20 17:17 ` Dave Hansen
2008-10-17 6:44 ` Cedric Le Goater
2008-10-17 7:08 ` Oren Laadan
2008-10-09 21:59 ` Greg Kurz
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=1223916223.29877.14.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=clg@fr.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=major@openvz.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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