mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oren Laadan <orenl@cs.columbia.edu>
To: Christoffer Dall <christofferdall@christofferdall.dk>
Cc: containers <containers@lists.linux-foundation.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [C/R ARM v2][PATCH 0/3] Linux Checkpoint-Restart - ARM port
Date: Sun, 20 Jun 2010 17:34:10 -0400	[thread overview]
Message-ID: <4C1E8952.7010503@cs.columbia.edu> (raw)
In-Reply-To: <1272318223-28438-1-git-send-email-christofferdall@christofferdall.dk>

Applied.

On 04/26/2010 05:43 PM, Christoffer Dall wrote:
> Following there will be two preparatory patches for an ARM port of the
> checkpoint-restart code and finally a third patch implementing the
> architecture-specific parts of c/r.
> 
> The preparatory patches consist of a partial syscall trace implementation
> for ARM and an eclone implementation for ARM. The syscall trace
> implementation provides only the needed functionality for c/r.
> 
> There is a separate patch for the user space code, which supports
> cross-compilation, extracting headers for ARM and an eclone implementation
> for ARM.
> 
> The kernel patches presented here are based on the ckpt-v21-rc6 patch set.
> 
> ---
> 
> CHANGELOG:
> 
> [2010-Apr-08] v2:
> 	- Systrace implementation now inspects process state to get the
> 	  system call number thereby avoiding extra work on system calls.
> 	- Removed __user attribute on long type in eclone implementation
> 	- Better check for architecture versions across C/R
> 	- Improved checking of user space ABI settings across C/R
> 	- Code simplifications
> 
> [2010-Mar-22] v1:
> 	- Initial version
> 	- Systrace implementation modified the system call entry path to
> 	  store the system call number globally in memory.
> 	- ARM implementation lightly tested
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
> 

      parent reply	other threads:[~2010-06-20 22:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 21:43 Christoffer Dall
2010-04-26 21:43 ` [C/R ARM v2][PATCH 1/3] ARM: Rudimentary syscall interfaces Christoffer Dall
2010-04-29  0:08   ` Roland McGrath
2010-04-26 22:36     ` [C/R ARM v2][PATCH] " Christoffer Dall
2010-04-26 21:43 ` [C/R ARM v2][PATCH 2/3] ARM: Add the eclone system call Christoffer Dall
2010-04-26 21:43 ` [C/R ARM v2][PATCH 3/3] c/r: ARM implementation of checkpoint/restart Christoffer Dall
2010-06-20 21:34 ` Oren Laadan [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=4C1E8952.7010503@cs.columbia.edu \
    --to=orenl@cs.columbia.edu \
    --cc=christofferdall@christofferdall.dk \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®