From: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: LXC+USER integrated patchset
Date: Wed, 10 Nov 2010 11:22:57 -0800 [thread overview]
Message-ID: <20101110192256.GA19346@us.ibm.com> (raw)
FYI,
I just uploaded a patchset for the lxc tree to sourceforge:
http://lxc.sourceforge.net/patches/lxc+usercr/lxc-0.7.2/lxc-patches/
Feel free to use this patchset to test/play with checkpoint/restart :-)
Excerpts from the 'cover-letter' in the patchset:
| These patches apply on top of lxc-0.7.2.
|
| The patches mainly pull user-cr into the lxc source tree and enable
| building LXC with integrated support for C/R.
|
| These patches should work with a recent kernel ( 2.6.32 or later) and
| with the ckpt-v22-dev branch of the Linux C/R tree:
|
| git://git.ncl.cs.columbia.edu/pub/git/linux-cr.git
|
| The FD_NOCHECKPOINT (which is an expermental patch) and NR_eclone should be
| the only changes dependent on kernel changes. The error from
|
| fcntl(FD_NOCHECKPOINT)
|
| is silently ignored for now, so it should not be a problem. But please
| report any problems you encounter :-)
Sukadev
reply other threads:[~2010-11-10 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101110192256.GA19346@us.ibm.com \
--to=sukadev-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
/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