[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1223557122.11830.14.camel@nimitz>
Date: Thu, 09 Oct 2008 05:58:42 -0700
From: Dave Hansen <dave@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Oren Laadan <orenl@...columbia.edu>, jeremy@...p.org,
arnd@...db.de, containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Alexander Viro <viro@...iv.linux.org.uk>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [RFC v6][PATCH 0/9] Kernel based checkpoint/restart
On Thu, 2008-10-09 at 14:46 +0200, Ingo Molnar wrote:
> * Oren Laadan <orenl@...columbia.edu> wrote:
>
> > These patches implement basic checkpoint-restart [CR]. This version
> > (v6) supports basic tasks with simple private memory, and open files
> > (regular files and directories only). Changes mainly cleanups. See
> > original announcements below.
>
> i'm wondering about the following productization aspect: it would be
> very useful to applications and users if they knew whether it is safe to
> checkpoint a given app. I.e. whether that app has any state that cannot
> be stored/restored yet.
Absolutely!
My first inclination was to do this at checkpoint time: detect and tell
users why an app or container can't actually be checkpointed. But, if I
get you right, you're talking about something that happens more during
the runtime of the app than during the checkpoint. This sounds like a
wonderful approach to me, and much better than what I was thinking of.
What kind of mechanism do you have in mind?
int sys_remap_file_pages(...)
{
...
oh_crap_we_dont_support_this_yet(current);
}
Then the oh_crap..() function sets a task flag or something?
-- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists