[PATCH 0/6] /proc/pid/checkpointable
dave at linux.vnet.ibm.com
Wed Mar 18 09:24:55 PDT 2009
On Wed, 2009-03-18 at 12:16 -0400, Oren Laadan wrote:
> My suggestions works for this two: we add a flag CR_CTX_DRYRUN; a task
> can ask to checkpoint itself, or another task, with CR_CTX_DRYRUN and
> the checkpoint code runs without actual effect. (If we don't want to
> expose the actual flag to userspace, then we simply use it in an
> implementation of a /proc/PID/checkpointable operation).
This mostly falls short answering the question "Where/when did I go
wrong?" Personally, I think that is critical for getting good bug
reports out of normal Joes that might not really be interested in c/r
development itself. It is like lockdep. The guys/gals posting those
reports really don't know about kernel locking, but they are able to
improve it anyway.
More information about the Containers