From: tgh <wwwwww4187@sina.com.cn>
To: Daniel Stodden <stodden@cs.tum.edu>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: code read problems
Date: Wed, 27 Feb 2008 17:37:28 +0800 [thread overview]
Message-ID: <47C52F58.1070008@sina.com.cn> (raw)
In-Reply-To: <1204026247.10344.41.camel@thinkpad.localdomain>
hi
thank you for your reply
and i read the code of xc_save.c and xc_restore.c, which maybe do the
function of VMsaving and VMrestoring, but i wander, if the code of
xc_save.c and xc_restore.c is called by some python code or c code
during migration or xm save and xm restore or not? the code of xc_save.c
is a main function ,and is it called by other program to do migration or
not ?
and in the code of xc_save.c, there seem no notification to the
xenstore or devbackend, and how are these VMdevbackends destroyed in the
dom0, when migration or save?
and in the code of xc_restore.c,there seems to be an existing
VMdomain,and the whole data from savefile or from migration,will load
into the VMdomain, is it? then ,what code call these code of xc_save
and xc_restore? i am confused
could you help me out
Thanks in advance
Daniel Stodden 写道:
> On Tue, 2008-02-26 at 19:22 +0800, tgh wrote:
>
>> could you reply in english, i could not read your letter
>>
>
> Don't bother. Just an autoreply generated to tell you the guy is on
> vacation.
>
> Regarding your problem: There is not much you can do to get some sort
> execution traces enabled automatically. You probably want to enable
> debugging when building Xen and the libraries. Then maybe add a couple
> of debug-print statements to the code, whereever you see fit.
>
> I believe migration support in xend and libxc should be understandable
> in isolation. The tricky parts are definitely done in C. Last time I
> checked, xend mainly performed a single call to the tools and library.
>
> Also note that random instrumentation of all code executed for
> translating and mapping of the domU address space within the hypervisor
> would probably soon get more verbose than you asked for, since some of
> the functions involved can be called at a comparatively high frequency.
>
> Rule 1 when digging your way through complex systems: Divide and
> Conquer. Division comes first. Understand one thing at a time, starting
> at a comparatively high-level, then selectively dig deeper.
>
> regards,
> daniel
>
>
>
>> clp@eclinso.com 写道:
>>
>>> Vielen Dank für Ihre Nachricht.
>>>
>>> Ich bin vom 22-02-08 bis 07-03-08 nicht im Hause und werde Ihre
>>>
>> E-Mail ab dem 10-03-07 bearbeiten.
>>
>>> In dringenden Fällen wenden Sie sich bitte an Herrn Fabio Lüdi, er
>>>
>> wird Ihnen gerne weiterhelfen.
>>
>>> Sie erreichen Herrn Lüdi unter:
>>> Phone +41 61 6666 406
>>> E-Mail fl@eclinso.com
>>>
>
>
next prev parent reply other threads:[~2008-02-27 9:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080226095701.50167.qmail@dhost033.magnet.ch>
2008-02-26 11:22 ` code read problems tgh
2008-02-26 11:44 ` Daniel Stodden
2008-02-27 9:37 ` tgh [this message]
2008-02-27 19:23 ` Mike Sun
2008-02-28 18:52 ` Brendan Cully
2008-02-28 20:53 ` Mike Sun
2008-02-29 6:44 ` tgh
2008-02-29 13:39 ` Daniel Stodden
2008-03-01 1:21 ` tgh
2008-03-04 5:41 ` tgh
2008-02-28 13:49 ` question about dominfo.completeRestore() tgh
2008-02-26 12:15 ` code read problems Christoph Egger
2008-02-26 17:20 ` pradeep singh rautela
2008-01-02 18:52 migrateDevices( ) ? Stefan Berger
2008-01-04 6:49 ` migration and relocation server? tgh
2008-02-26 9:56 ` code read problems 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=47C52F58.1070008@sina.com.cn \
--to=wwwwww4187@sina.com.cn \
--cc=stodden@cs.tum.edu \
--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.