From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Martin Schwidefsky <schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Subject: Re: [RFC PATCH 0/2] cr: Introduce s390x checkpoint/restart code
Date: Thu, 15 Jan 2009 16:25:39 -0600 [thread overview]
Message-ID: <20090115222539.GA24296@us.ibm.com> (raw)
In-Reply-To: <1232014244.30152.19.camel@localhost>
Quoting Martin Schwidefsky (schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org):
> What is left are the pgstes tables. After you forked the new process
> that is used to restart a KVM enabled process you need to call
> s390_enable_sie(), preferably before you recreate the VMAs.
So, let's say we're checkpointing 3 tasks in a s390-kvm.
Now we restart them outside of kvm. Some process will
fork(), exec() some restart program, which will in turn
fork() twice, then each of those programs will call
sys_restart(), read the info pertaining to the checkpoint
task they are to re-create, and set themselves up.
Should the s390_enable_sie() then not be correctly set
by the system automatically? So whether or not I'm
restarting in kvm, the kvm_arch_create_vm() for s390
will have been called?
Or do I misunderstand?
thanks,
-serge
next prev parent reply other threads:[~2009-01-15 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 5:05 [RFC PATCH 0/2] cr: Introduce s390x checkpoint/restart code Serge E. Hallyn
[not found] ` <20090115050523.GA10415-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-01-15 5:06 ` [RFC PATCH 1/2] c/r: hook checkpoint and restart for s390 Serge E. Hallyn
2009-01-15 5:06 ` [RFC PATCH 2/2] cr: s390: fill in the read/write routines Serge E. Hallyn
2009-01-15 9:39 ` [RFC PATCH 0/2] cr: Introduce s390x checkpoint/restart code Martin Schwidefsky
2009-01-15 9:55 ` Oren Laadan
[not found] ` <496F082C.3020008-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-01-15 10:10 ` Martin Schwidefsky
2009-01-15 22:25 ` Serge E. Hallyn [this message]
2009-01-15 16:29 ` Serge E. Hallyn
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=20090115222539.GA24296@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=schwidefsky-tA70FqPdS9bQT0dZR+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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox