From: Adrian Reber <adrian@lisas.de>
To: linux-kernel@vger.kernel.org
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Pavel Emelyanov" <xemul@parallels.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Oren Laadan" <orenl@cs.columbia.edu>,
matt.helsley@gmail.com,
"Peter Väterlein" <Peter.Vaeterlein@hs-esslingen.de>
Subject: linux-cr ported to 3.2-rc1
Date: Mon, 14 Nov 2011 16:13:00 +0100 [thread overview]
Message-ID: <20111114151300.GT16442@lisas.de> (raw)
I have ported the linux-cr patches from www.linux-cr.org/pub/git/linux-cr.git
to the latest kernel (3.2-rc1). The tests (on x86_64) I have done so far
were successful. My repository with the C/R patches on top of 3.2-rc1 is
currently at:
http://lisas.de/~adrian/linux-cr.git
The development on the linux-cr tree hast stopped sometime around 2.6.37
and although those patches have gone through many revisions I am not sure
about the latest state of those patches concerning inclusion. At what
point has the discussion stopped and why?
I have seen patches from Pavel about another approach for
checkpointing/restarting but I haven't heard anything about
that during the last months.
What are the chances to get one of the checkpointing/restarting
implementations included. What is still missing from the one I used?
What is the latest state of Pavel's patches?
Adrian
next reply other threads:[~2011-11-14 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 15:13 Adrian Reber [this message]
2011-11-14 15:20 ` linux-cr ported to 3.2-rc1 Pavel Emelyanov
2011-11-15 18:29 ` Serge E. Hallyn
2011-11-16 8:19 ` Pavel Emelyanov
2012-01-05 21:07 ` Adrian Reber
2012-01-10 9:41 ` Pavel Emelyanov
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=20111114151300.GT16442@lisas.de \
--to=adrian@lisas.de \
--cc=Peter.Vaeterlein@hs-esslingen.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.helsley@gmail.com \
--cc=orenl@cs.columbia.edu \
--cc=serge@hallyn.com \
--cc=xemul@parallels.com \
/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.