From mboxrd@z Thu Jan 1 00:00:00 1970 From: Edwin Zhai Subject: Re: Detecting deadlocks with hypervisor.. Date: Sun, 19 Mar 2006 18:16:43 +0800 Message-ID: <20060319101643.GI28916@edwin-gen.ccr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Thileepan Subramaniam Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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