All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andre Przywara" <andre.przywara@amd.com>
To: tgh <wwwwww4187@sina.com.cn>
Cc: xen-devel@lists.xensource.com
Subject: Re: migration and restore?
Date: Tue, 08 Jan 2008 13:16:31 +0100	[thread overview]
Message-ID: <4783699F.20201@amd.com> (raw)
In-Reply-To: <477DEAA4.3040204@sina.com.cn>

> i read the code of migration, and i fail to find the counterpart code of 
> migration , which deal with the restoration of VM in the destination 
> node, and i read the code of /tools/libxc/xc_domain_restore.c ,but the 
> function of xc_domain_restore() seems not to be the one for the 
> migration, it seems not support the restore of the iterative copy of the 
> VM memory state ,is it? or how does it deal with the work?

Maybe the missing pieces you are looking for are in the xend (Python) 
code? In line 205 (or so) in tools/pyhton/xen/xend/XendDomainInfo.py you 
will find the high level function "restore". This method calls 
XendDomainInfo.resume (line 446) and triggers the necessary actions 
here. Another file to look in is XendCheckpoint.py, here you'll find the 
method "restore" (line 154). Some Migration code is also in XendDomain.py.
You can get more info if you enable debugging, do a live migration (to 
localhost) and look in xend.log for "Saving memory pages" or "Reloading 
memory pages". From here you will find the corresponding code (maybe by 
just grepping for the log message text).
I found line 427 in xc_domain_restore.c, the code following this line 
deals with the restoring of the frames. From my perspective there is 
everything needed in there.

Hope that helps!

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
AMD Saxony Limited Liability Company & Co. KG,
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896, General Partner authorized
to represent: AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy

  reply	other threads:[~2008-01-08 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 22:18 xentrace_setmask badly broken? Dan Magenheimer
2008-01-03  1:51 ` Mark Williamson
2008-01-03  3:42   ` Rob Gardner
2008-01-04  8:13   ` migration and restore? tgh
2008-01-08 12:16     ` Andre Przywara [this message]
2008-01-08 12:57       ` Daniel Stodden
2008-02-27  1:36         ` tgh
2008-02-27  3:41           ` failure about xc_save tgh

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=4783699F.20201@amd.com \
    --to=andre.przywara@amd.com \
    --cc=wwwwww4187@sina.com.cn \
    --cc=xen-devel@lists.xensource.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.