 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] xm pause causing lockup
| To: | Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] xm pause causing lockup |
| From: | Kip Macy <kip.macy@xxxxxxxxx> |
| Date: | Wed, 13 Apr 2005 20:18:46 -0700 |
| Cc: | xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
| Delivery-date: | Thu, 14 Apr 2005 03:18:41 +0000 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=q/8Ev0F4gNJG0Gq6NKp4EaQsVqz/+xHseFe0LnrEuYlyEhGEB4F+CxsbWtg7UKbAQaIpRabmUFV28dh0VJd+UueQWfmR98Rwba9zwTLEJ4WpFyeBrcNNXHZdTcBS1frwdfv8LOnR4pDChilhPEnkeqJx/+SK8ZzkMidtOfeU2hg= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <cafff1b5d55bd618912085cc8e2b34dc@xxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <b1fa291705041319464ffdb42a@xxxxxxxxxxxxxx> <4afce18847157fad34cd38e14fb83c2c@xxxxxxxxxxxx> <b1fa291705041320031af8f565@xxxxxxxxxxxxxx> <cafff1b5d55bd618912085cc8e2b34dc@xxxxxxxxxxxx> |
| Reply-to: | Kip Macy <kip.macy@xxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On 4/13/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 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.
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.
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] address space reorganization, Kip Macy |
|---|---|
| Next by Date: | Re: [Xen-devel] address space reorganization, Jacob Gorm Hansen |
| Previous by Thread: | Re: [Xen-devel] xm pause causing lockup, Keir Fraser |
| Next by Thread: | Re: [Xen-devel] xm pause causing lockup, Kip Macy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
