From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: Adrian Reber <adrian-5+Cda9B46AM@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>,
Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: linux-cr ported to 3.1
Date: Thu, 27 Oct 2011 14:41:25 +0000 [thread overview]
Message-ID: <20111027144125.GA14452@hallyn.com> (raw)
In-Reply-To: <20111027142731.GT20908-5+Cda9B46AM@public.gmane.org>
Quoting Adrian Reber (adrian-5+Cda9B46AM@public.gmane.org):
>
> I have ported the linux-cr patches from www.linux-cr.org/pub/git/linux-cr.git
> to the latest kernel (3.1). What I have tested so far it still seems to work.
Wow, that's great!
Since you went to the trouble of doing this, can we assume you have a pretty
strong interest in this set? :) If so,
> Can anybody tell me what the latest state of these patches was?
> Development seemed to have stopped after 2.6.37 and with the wiki[1] being
> down I do not know if anybody is still working on these patches. What
Matt and Dan, if there is outside interest, are you able to help out at
all? Are you still using this set at all?
Oren, what's your status?
> was the latest status about those patches being integrated into
> mainline? Is someone still trying to get it included?
There is a new upstream effort based around pushing smaller debugging-style
patches, which rather than adding a 'sys_checkpoint' syscall, allow userspace
to get the information they need to reconstruct a process set. Several people,
Daniel (Cc:d) included, seem to prefer this approach. See
http://lwn.net/Articles/452184/ for instance.
You might peruse the recent lkml threads (and the above article). If you are
ok with that approach, you might consider joining them. AFAICS they've not
done much in the last few months, though I may just have missed it.
> Here is my git tree with all the patches on top of 3.1.
>
> http://lisas.de/~adrian/linux-cr.git
>
> Adrian
>
> [1] http://ckpt.wiki.kernel.org/
-serge
next prev parent reply other threads:[~2011-10-27 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 14:27 linux-cr ported to 3.1 Adrian Reber
[not found] ` <20111027142731.GT20908-5+Cda9B46AM@public.gmane.org>
2011-10-27 14:41 ` Serge E. Hallyn [this message]
[not found] ` <20111027144125.GA14452-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2011-10-28 12:52 ` Adrian Reber
2011-10-28 20:35 ` Dan Smith
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=20111027144125.GA14452@hallyn.com \
--to=serge-a9i7lubdfnhqt0dzr+alfa@public.gmane.org \
--cc=adrian-5+Cda9B46AM@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.