From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org,
Linux Containers <containers@lists.osdl.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Mike Waychison <mikew@google.com>, Andrew Morton <akpm@osdl.org>,
linux-s390@vger.kernel.org, linux390@de.ibm.com
Subject: Re: [PATCH] c/r: define s390-specific checkpoint-restart code
Date: Wed, 28 Jan 2009 09:37:17 -0600 [thread overview]
Message-ID: <20090128153717.GA25153@us.ibm.com> (raw)
In-Reply-To: <497F3F9F.2000803@cs.columbia.edu>
Quoting Oren Laadan (orenl@cs.columbia.edu):
>
>
> Serge E. Hallyn wrote:
> > Implement the s390 arch-specific checkpoint/restart helpers. This
>
> Thanks for the patch.
>
> I will assume that the s390 specifics are correct...
>
> > is on top of Oren Laadan's c/r code (which so far was x86_32-only)
> > submitted here: http://lkml.org/lkml/2008/12/29/38, plus two more
> > patches by Nathan Lynch to fix some 64-bit issues (see
> > https://lists.linux-foundation.org/pipermail/containers/2009-January/015313.html
> > and
> > https://lists.linux-foundation.org/pipermail/containers/2009-January/015314.html
> > ).
>
> ckpt-v13 already has these two fixed.
>
> >
> > With these, I am able to checkpoint and restart simple programs as per
> > Oren's patch intro. While on x86 I never had to freeze a single task
> > to checkpoint it, on s390 I do need to. That is a prereq for consistent
> > snapshots (esp with multiple processes) anyway so I don't see that as
> > a problem.
> >
> > Oren, should we be putting a byte at the front of the format to
> > specify the architecture?
>
> If we add a field to 'struct cr_hdr_head', then we'll need arch-dependent
> code in a non-arch dependent source, to ensure that no two architectures
> choose the same value as an identifier.
>
> Can we not use the 'machine' string fiels in 'struct cr_hdr_head' - and
> then additional classification can take place in cr_read/write_head_arch() ?
Huh, yes, I somehow missed that.
> > +#define DEBUG 1
> > +
> > #include <linux/version.h>
> > #include <linux/sched.h>
> > #include <linux/ptrace.h>
> > diff --git a/checkpoint/restart.c b/checkpoint/restart.c
> > index 6b4cd75..f65a63e 100644
> > --- a/checkpoint/restart.c
> > +++ b/checkpoint/restart.c
> > @@ -8,6 +8,8 @@
> > * distribution for more details.
> > */
> >
> > +#define DEBUG 1
> > +
> > #include <linux/version.h>
> > #include <linux/sched.h>
> > #include <linux/wait.h>
> >
>
> Probably unrelated ?
Yup. Will send a new version inc. your changes and against
v13 later this week.
thanks,
-serge
prev parent reply other threads:[~2009-01-28 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 17:36 [PATCH] c/r: define s390-specific checkpoint-restart code Serge E. Hallyn
2009-01-27 17:08 ` Oren Laadan
2009-01-28 15:37 ` Serge E. Hallyn [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=20090128153717.GA25153@us.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=containers@lists.osdl.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=mikew@google.com \
--cc=mingo@elte.hu \
--cc=orenl@cs.columbia.edu \
--cc=tglx@linutronix.de \
/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