WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] VMX status report 12033:b21246720fde

To: "Li, Xin B" <xin.b.li@xxxxxxxxx>, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] VMX status report 12033:b21246720fde
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 01 Nov 2006 07:40:30 +0000
Delivery-date: Thu, 02 Nov 2006 13:54:32 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <B30DA1341B0CFA4893EF8A36B40B5C5D55AA92@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acb8nlQkpaZ430hoSVmzmsU4spEvlAAIcJHwADDwYgAAAUpUjA==
Thread-topic: [Xen-devel] VMX status report 12033:b21246720fde
User-agent: Microsoft-Entourage/11.2.5.060620


On 1/11/06 7:09 am, "Li, Xin B" <xin.b.li@xxxxxxxxx> wrote:

> Hi Keir, this bug is caused by a dead spin lock in printk: printk will
> call __printk_ratelimit, but this guy may call printk again ( when lost
>> 0 ).
> After removing the call to printk in __printk_ratelimit, this bug is
> gone.

Thanks, I'll investigate the right fix.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>