From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Greg Kurz <gkurz@fr.ibm.com>
Cc: Oren Laadan <orenl@cs.columbia.edu>, Ingo Molnar <mingo@elte.hu>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
containers@lists.linux-foundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 1/2] Track in-kernel when we expect checkpoint/restart to work
Date: Fri, 10 Oct 2008 09:36:43 -0700 [thread overview]
Message-ID: <1223656603.11830.50.camel@nimitz> (raw)
In-Reply-To: <1223656489.10017.33.camel@localhost.localdomain>
On Fri, 2008-10-10 at 18:34 +0200, Greg Kurz wrote:
> This flag is weak... testing it gives absolutly no hint whether the
> checkpoint may succeed or not. As it is designed now, a user can only be
> aware that checkpoint is *forever* denied. I agree that it's only useful
> as a "flexible CR todo list".
Cool, so everyone agrees the patch is useful!
-- Dave
next prev parent reply other threads:[~2008-10-10 16:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 19:04 [RFC][PATCH 1/2] Track in-kernel when we expect checkpoint/restart to work Dave Hansen
2008-10-09 19:04 ` [RFC][PATCH 2/2] first callers of process_deny_checkpoint() Dave Hansen
2008-10-09 19:43 ` Serge E. Hallyn
2008-10-09 20:54 ` Dave Hansen
2008-10-10 8:46 ` Ingo Molnar
2008-10-10 13:17 ` Rafael J. Wysocki
2008-10-10 14:54 ` Ingo Molnar
2008-10-10 19:53 ` Rafael J. Wysocki
2008-10-10 19:53 ` Ingo Molnar
2008-10-10 20:40 ` Len Brown
2008-10-10 22:57 ` Rafael J. Wysocki
2008-10-11 13:48 ` Pavel Machek
2008-10-11 15:00 ` Ingo Molnar
2008-10-10 10:27 ` Cedric Le Goater
2008-10-10 8:41 ` Daniel Lezcano
2008-10-10 10:17 ` Cedric Le Goater
2008-10-10 14:04 ` Serge E. Hallyn
2008-10-10 16:45 ` Greg Kurz
2008-10-10 17:13 ` Serge E. Hallyn
2008-10-10 17:28 ` Dave Hansen
2008-10-13 8:20 ` Greg Kurz
2008-10-10 8:20 ` [RFC][PATCH 1/2] Track in-kernel when we expect checkpoint/restart to work Greg Kurz
2008-10-10 8:37 ` Daniel Lezcano
2008-10-10 8:47 ` Greg Kurz
2008-10-10 10:11 ` Oren Laadan
2008-10-10 14:59 ` Ingo Molnar
2008-10-10 15:17 ` Oren Laadan
2008-10-10 15:28 ` Ingo Molnar
2008-10-10 16:34 ` Greg Kurz
2008-10-10 16:36 ` Dave Hansen [this message]
2008-10-10 20:57 ` Daniel Lezcano
2008-10-10 17:18 ` Chris Friesen
2008-10-13 8:18 ` Greg Kurz
2008-10-13 16:46 ` Serge E. Hallyn
2008-10-10 16:33 ` Dave Hansen
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=1223656603.11830.50.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=containers@lists.linux-foundation.org \
--cc=dlezcano@fr.ibm.com \
--cc=gkurz@fr.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=orenl@cs.columbia.edu \
/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