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-ia64-devel

Re: [Xen-devel] Re: [Xen-ia64-devel] Weekly benchmark results [ww24]

To: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-ia64-devel] Weekly benchmark results [ww24]
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Tue, 20 Jun 2006 11:06:36 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "yo.fujita" <yo.fujita@xxxxxxxxxxxxxxxx>, "'You, Yongkang'" <yongkang.you@xxxxxxxxx>, Steven.Hand@xxxxxxxxxxxx, 'Alex Williamson' <alex.williamson@xxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Jun 2006 03:07:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Message from Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx> of "Tue, 20 Jun 2006 14:26:04 +0900." <200606200526.k5K5QWlK009993@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
>==================
>STATUS
>==================
>I do the heavy load test of create/destroy.
>CREDIT scheduler(cshed_schedule) checks BUG_ON(!vcpu_running) at the end of co
de.
>It makes error.
>The reason is that
>atomic_inc(&v->pausecnt)@vcpu_pause() is called without lock.
>(spin_lock(&schedule_data[cpu].schedule_lock))
>This lock-less "pausecnt" makes vcpu_running state changing 
>during the lock of 
>spin_lock_irq(&schedule_data[cpu].schedule_lock)@__enter_schduler().
>The code of cshed_schedule exists within this lock. 

Thanks for this - we have also reproduced. 
The assertation was in fact bogus as you surmised. Have checked in a 
fix. 

cheers,

S.

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