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] Hypervisor crash(!) on xl cpupool-numa-split

To: Stephan Diestelhorst <stephan.diestelhorst@xxxxxxx>
Subject: Re: [Xen-devel] Hypervisor crash(!) on xl cpupool-numa-split
From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date: Thu, 03 Feb 2011 10:18:16 +0100
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, "Przywara, Andre" <Andre.Przywara@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Thu, 03 Feb 2011 01:19:10 -0800
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1296724699; x=1328260699; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; z=Message-ID:=20<4D4A72D8.3020502@xxxxxxxxxxxxxx>|Date:=20 Thu,=2003=20Feb=202011=2010:18:16=20+0100|From:=20Juergen =20Gross=20<juergen.gross@xxxxxxxxxxxxxx>|MIME-Version: =201.0|To:=20Stephan=20Diestelhorst=20<stephan.diestelhor st@xxxxxxx>|CC:=20George=20Dunlap=20<George.Dunlap@xxxxxx rix.com>,=20=0D=0A=20"Przywara,=20Andre"=20<Andre.Przywar a@xxxxxxx>,=0D=0A=20"xen-devel@xxxxxxxxxxxxxxxxxxx"=20<xe n-devel@xxxxxxxxxxxxxxxxxxx>,=20=0D=0A=20Keir=20Fraser=20 <keir@xxxxxxx>,=0D=0A=20Ian=20Jackson=20<Ian.Jackson@xxxx itrix.com>|Subject:=20Re:=20[Xen-devel]=20Hypervisor=20cr ash(!)=20on=20xl=20cpupool-numa-split|References:=20<4D41 FD3A.5090506@xxxxxxx>=09<201102021539.06664.stephan.diest elhorst@xxxxxxx>=09<4D4974D1.1080503@xxxxxxxxxxxxxx>=09<2 01102021701.05665.stephan.diestelhorst@xxxxxxx>=20<4D4A43 B7.5040707@xxxxxxxxxxxxxx>|In-Reply-To:=20<4D4A43B7.50407 07@xxxxxxxxxxxxxx>; bh=o6ePk2KHF5rrzAgbp7jL2ArJStdS95h51dtgkNhb4hA=; b=fi3xfupwNBfNZ5548/cHrtzjAxLlTcHk3Cq+kmxgVvoBONo7TpuVqtvD DlVbUZpsDMr+FhUIr67yWkX7lMpDx2+uqXPb+KCZ3QQemy22TAGQDDglJ QTMflzbBHjHWDlAjmvrUq464+fxTIVhBzZ0r2tUtMjvEa3RlNbKZfFNiA y55fC/NE6Q08xXvNlr6srPJVvJEahrSSYaRbyQblHkZHqZj2gl+OI2x0V DEsqSsMfcCyYBIVGxNLSFlIfbh715;
Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=C6r/yCIVyeUUPR7KYzLF+Sso8iImVipQK/uaAd4hczra6YMjo7poPQGu s58snPd5VHh0n323+8XHDDyE7ZdFlnbPcxsyJ0cEmsylbHUWPasztU3HP +dXVPSTtI0bQeBDqyg2an/JUrS5FX9xsdyGflIJfl3CMK3uYG3vPuf85S eIghiMqvk2LtEq0df+qFgYR5J82DbrDYWD1n8djIVbGd/mFZ0EBXYMV/O EM238gWd+P9vKRvVnRG7/OOTN4djs;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D4A43B7.5040707@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Fujitsu Technology Solutions
References: <4D41FD3A.5090506@xxxxxxx> <201102021539.06664.stephan.diestelhorst@xxxxxxx> <4D4974D1.1080503@xxxxxxxxxxxxxx> <201102021701.05665.stephan.diestelhorst@xxxxxxx> <4D4A43B7.5040707@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101226 Iceowl/1.0b1 Icedove/3.0.11
Andre, Stephan,

could you give the attached patch a try?
It moves the cpu assigning/unassigning into a tasklet always executed on the
cpu to be moved. This should avoid critical races.

Regarding Stephans rant:
You should be aware that the main critical sections are only in the tasklets.
The locking in the main routines is needed only to avoid the cpupool to be
destroyed in between.

I'm not sure whether the master_ticker patch is still needed. It seems to
break something, as my machine hung up after several 100 cpu moves (without
the new patch). I'm still investigating this problem.


Juergen

--
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

Attachment: cpupool-idle.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>