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] cpuidle causing Dom0 soft lockups

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] cpuidle causing Dom0 soft lockups
From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date: Tue, 02 Feb 2010 09:13:30 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, ke.yu@xxxxxxxxx
Delivery-date: Tue, 02 Feb 2010 00:13:49 -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=1265098476; x=1296634476; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Juergen=20Gross=20<juergen.gross@xxxxxxxxxxxxxx> |Subject:=20Re:=20[Xen-devel]=20cpuidle=20causing=20Dom0 =20soft=20lockups|Date:=20Tue,=2002=20Feb=202010=2009:13: 30=20+0100|Message-ID:=20<4B67DEAA.7090208@xxxxxxxxxxxxxx >|To:=20Jan=20Beulich=20<JBeulich@xxxxxxxxxx>|CC:=20Keir =20Fraser=20<keir.fraser@xxxxxxxxxxxxx>,=20ke.yu@xxxxxxxx m,=20=0D=0A=20"xen-devel@xxxxxxxxxxxxxxxxxxx"=20<xen-deve l@xxxxxxxxxxxxxxxxxxx>|MIME-Version:=201.0 |Content-Transfer-Encoding:=207bit|In-Reply-To:=20<4B67E8 5E020000780002D1A0@xxxxxxxxxxxxxxxxxx>|References:=20<4B5 8402E020000780002B3FE@xxxxxxxxxxxxxxxxxx>=09<C77DE51B.6F8 9%keir.fraser@xxxxxxxxxxxxx>=20<4B67E85E020000780002D1A0@ vpn.id2.novell.com>; bh=y1cukXadCje6fC99fDJOX/sHYLoL/0+KCpq/tV9ahFY=; b=P1m+9T+pG20H8B2QJrX5lFS50SwiRK1Jrjx6rBy0WvU7BD+TIGUNgQao FFCQGY4BcQhQSfj46cD7jgPYFaI4NFngOlk71NVXvlODmLp7TSUnBDZ18 F5LrMqcQXe7POuLL/DLUueLbmS0aOLRy5t4m/+uGIw6IgyTi7iVhb2Z9H /Qx3W8HwM8s1Wr6PqfpuKJ++pkRENmpTAwZEUbAx5SYQFUQApDlApgZqu lQmxIFzVxG6Eplv8ey2YM2duU8FTD;
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:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=WE44XexBfHZ2GvxZ0e73aUDDQTBxyXJQ3KzWudHZEAflLKaDxnIHtEle V3jmYYvXp9ntKJrl6h18mm2swKXliYFiMOAKe20H0oY2INepP4MjGJ4Ut fQmhYzZW9MaeVpVo8iQItxg6pIN6POGUBms+VfeMnODlX0VuMDSgp9sS5 Lsa39t4GxFbt6801VibfEjz5BnYEjlUdqJNIg/jITRenCUGpt4WgJyGQg ts9PTmmctwYV9kbk3BcSJ8xTs6WOK;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B67E85E020000780002D1A0@xxxxxxxxxxxxxxxxxx>
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: <4B58402E020000780002B3FE@xxxxxxxxxxxxxxxxxx> <C77DE51B.6F89%keir.fraser@xxxxxxxxxxxxx> <4B67E85E020000780002D1A0@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707)
Jan Beulich wrote:
>>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 21.01.10 12:03 >>>
>> On 21/01/2010 10:53, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>>> I can see your point. But how can you consider shipping with something
>>> apparently severely broken. As said before - the fact that this manifests
>>> itself by hanging many-vCPU Dom0 has the very likely implication that
>>> there are (so far unnoticed) problems with smaller Dom0-s. If I had a
>>> machine at hand that supports C3, I'd try to do some measurements
>>> with smaller domains...
>> Well it's a fallback I guess. If we can't make progress on solving it then I
>> suppose I agree.
> 
> Just fyi, we now also have seen an issue on a 24-CPU system that went
> away with cpuidle=0 (and static analysis of the hang hinted in that
> direction). All I can judge so far is that this likely has something to do
> with our kernel's intensive use of the poll hypercall (i.e. we see vCPU-s
> not waking up from the call despite there being pending unmasked or
> polled for events).

Interesting. I see this problem on a 4-core system.
Can I help investigating?

Data of my machine (Fujitsu TX300-S5):

# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 26
model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
stepping        : 5
...


Juergen

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

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