From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: xm pause causing lockup Date: Wed, 13 Apr 2005 20:18:46 -0700 Message-ID: References: <4afce18847157fad34cd38e14fb83c2c@cl.cam.ac.uk> Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On 4/13/05, Keir Fraser wrote: > Probably easiest way to trace this is with printk's in Xen. The guts of > the work is done by domain_pause_by_systemcontroller() in xen/sched.h. > This in turn calls domain_sleep() in common/schedule.c.=20 I traced through that code a while back when trying to decide what to call from the int3 handler. A particularly > interesting place to look will be teh synchronous spin loop at the end > of domain_sleep -- if the paused domain isn't descheduled for some > weird reason then the spin loop would never exit and domain0 would > hang. Good point. It will be interesting to see.=20 I sometimes wonder if I should keep some of the buggy versions of FreeBSD around for regression testing as they trigger some interesting behaviours in xen and xend. -Kip