From: Greg Kurz <gkurz@fr.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
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>
Subject: Re: [RFC v6][PATCH 0/9] Kernel based checkpoint/restart
Date: Thu, 09 Oct 2008 23:59:33 +0200 [thread overview]
Message-ID: <1223589573.6117.66.camel@localhost.localdomain> (raw)
In-Reply-To: <20081009131701.GA21112@elte.hu>
On Thu, 2008-10-09 at 15:17 +0200, Ingo Molnar wrote:
> yeah, something like that. A key aspect of it is that is has to be very
> low-key on the source code level - we dont want to sprinkle the kernel
> with anything ugly. Perhaps something pretty explicit:
>
> current->flags |= PF_NOCR;
>
> as we do the same thing today for certain facilities:
>
> current->flags |= PF_NOFREEZE;
>
> you probably want to hide it behind:
>
> set_current_nocr();
>
Being uncheckpointable is a transient and hopefully reversible state.
A set_current_cr() function is also needed and should be called at some
time to avoid abusive denials of checkpoint (DoC ?).
With the sys_remap_file_pages() example, set_current_cr() should be
called somewhere in sys_munmap() or even sys_remap_file_pages(). Some
code should be added to detect the mapping that lead the nocr state is
removed (a flag on the affected vma?) or fixed (checking the linearity
of mapping?). Would this code be low-key enough ?
> and have a set_task_nocr() as well, in case there's some proxy state
> installed by another task.
>
> Via such wrappers there's no overhead at all in the
> !CONFIG_CHECKPOINT_RESTART case.
>
> Plus you could drive the debug mechanism via it as well, by using a
> trivial extension of the facility:
>
> set_current_nocr("CR: sys_remap_file_pages not supported yet.");
> ...
> set_task_nocr(t, "CR: PI futexes not supported yet.");
>
> Ingo
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
--
Gregory Kurz gkurz@fr.ibm.com
Software Engineer @ IBM/Meiosys http://www.ibm.com
Tel +33 (0)534 638 479 Fax +33 (0)561 400 420
"Anarchy is about taking complete responsibility for yourself."
Alan Moore.
--
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>
prev parent reply other threads:[~2008-10-09 21:59 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
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 [this message]
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=1223589573.6117.66.camel@localhost.localdomain \
--to=gkurz@fr.ibm.com \
--cc=arnd@arndb.de \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--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