All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH 1/1] switch s390 sys_checkpoint as well
Date: Wed, 27 Jan 2010 16:06:48 -0500	[thread overview]
Message-ID: <4B60AAE8.3000206@cs.columbia.edu> (raw)
In-Reply-To: <20100127200111.GA24277-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>


got it.

Serge E. Hallyn wrote:
> I thought I had sent this before and was surprised to not see it
> in ckpt-v19-rc2.6, but actually it's not in my Sent folder so I
> think I was remiss...
> 
> Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> ---
>  arch/s390/kernel/process.c |    9 +++++++++
>  1 files changed, 9 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/s390/kernel/process.c b/arch/s390/kernel/process.c
> index 087f52c..ef66fa3 100644
> --- a/arch/s390/kernel/process.c
> +++ b/arch/s390/kernel/process.c
> @@ -242,7 +242,16 @@ SYSCALL_DEFINE4(clone, unsigned long, newsp, unsigned long, clone_flags,
>  }
>  
>  #ifdef CONFIG_CHECKPOINT
> +extern long do_sys_checkpoint(pid_t pid, int fd, unsigned long flags,
> +				int logfd);
>  extern long do_sys_restart(pid_t pid, int fd, unsigned long flags, int logfd);
> +
> +SYSCALL_DEFINE4(checkpoint, pid_t, pid, int, fd, unsigned long, flags,
> +		int, logfd)
> +{
> +	return do_sys_checkpoint(pid, fd, flags, logfd);
> +}
> +
>  SYSCALL_DEFINE4(restart, pid_t, pid, int, fd, unsigned long, flags,
>  		int, logfd)
>  {

      parent reply	other threads:[~2010-01-27 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 20:01 [PATCH 1/1] switch s390 sys_checkpoint as well Serge E. Hallyn
     [not found] ` <20100127200111.GA24277-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-27 21:06   ` 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=4B60AAE8.3000206@cs.columbia.edu \
    --to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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.