All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edwin Zhai <edwin.zhai@intel.com>
To: Thileepan Subramaniam <thileepan_@hotmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Detecting deadlocks with hypervisor..
Date: Sun, 19 Mar 2006 18:16:43 +0800	[thread overview]
Message-ID: <20060319101643.GI28916@edwin-gen.ccr> (raw)
In-Reply-To: <BAY108-F1559EBC532E859A0955BCF6DA0@phx.gbl>

On Sat, Mar 18, 2006 at 06:14:09PM -0800, Thileepan Subramaniam wrote:
> I tried to follow the flow of the .py files (XendCheckpoint.py etc.). These 
> seem to be called when I run 'xm save'. But beyond a point I am not sure what 
> the python scripts do. I also see some libxc files such as xc_linux_save.c, 
> but I am not sure who is using it (Dom-0 or Xen or the XenU). Can someone help 
> me by explaining me what happens behind the scene when "xm save" is called ? 
> Is there any good documentation explaining which actions are done by which 
> layers (eg: python layer, C layer etc).
python layer only save some domain info, i think.
then the app xc_save will be called, that in turn call xc_linux_save.  
xc_linux_save save all the memory and vcpu context of the guest.

-- 
thanks,
edwin

  parent reply	other threads:[~2006-03-19 10:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19  2:14 Detecting deadlocks with hypervisor Thileepan Subramaniam
2006-03-19  6:37 ` Randy Thelen
2006-03-19 10:16 ` Edwin Zhai [this message]
2006-03-19 13:17 ` Ewan Mellor
2006-03-24 18:57   ` T S
2006-03-24 19:04   ` T S
2006-03-24 19:24     ` Anthony Liguori
2006-03-24 20:30       ` T S
2006-04-07 17:11       ` T S
2006-04-07 17:22         ` Keir Fraser
2006-04-07 17:45           ` Anthony Liguori
2006-04-07 17:41         ` Anthony Liguori
2006-04-08  1:47           ` T S
2006-04-08 14:38             ` Anthony Liguori
2006-03-19 16:30 ` Anthony Liguori

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=20060319101643.GI28916@edwin-gen.ccr \
    --to=edwin.zhai@intel.com \
    --cc=thileepan_@hotmail.com \
    --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.