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: "Ke Yu" <ke.yu@xxxxxxxxx>,"Kevin Tian" <kevin.tian@xxxxxxxxx>
Subject: RE: [Xen-devel] cpuidle causing Dom0 soft lockups
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 08 Feb 2010 08:36:57 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, KeirFraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 08 Feb 2010 00:37:16 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <73BDC2BA3DA0BD47BAAEE12383D407EFF8E008F8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <4B58402E020000780002B3FE@xxxxxxxxxxxxxxxxxx> <C77DE51B.6F89%keir.fraser@xxxxxxxxxxxxx> <4B67E85E020000780002D1A0@xxxxxxxxxxxxxxxxxx> <8B81FACE836F9248894A7844CC0BA814250B940CFF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B6BE984020000780002DDF9@xxxxxxxxxxxxxxxxxx> <73BDC2BA3DA0BD47BAAEE12383D407EF35C82CF4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B6BEF70020000780002DE0F@xxxxxxxxxxxxxxxxxx> <73BDC2BA3DA0BD47BAAEE12383D407EF35C82D27@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B6C02EF020000780002DE56@xxxxxxxxxxxxxxxxxx> <73BDC2BA3DA0BD47BAAEE12383D407EF35C82D49@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B6C4061020000780002DEFB@xxxxxxxxxxxxxxxxxx> <73BDC2BA3DA0BD47BAAEE12383D407EFF8E008F8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> "Tian, Kevin" <kevin.tian@xxxxxxxxx> 06.02.10 02:50 >>>
>>Next I'll do is try to detect when the duty CPU is de-scheduled, and
>>move on the duty to one that is scheduled (i.e. one that is currently
>>executing timer_interrupt()).
>>
>
>It's still possible that you move duty to one active CPU, while that
>active CPU is in stop_hz_timer with interrupt disabled. In that case,
>again no one is able to update jiffies and again stale jiffies can be
>observed... 

No, since the first thing a CPU entering stop_hz_timer() does is
relinquish the duty of updating jiffies.

Jan


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