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>, Ke Yu <ke.yu@xxxxxxxxx>, Kevin Tian <kevin.tian@xxxxxxxxx>
Subject: Re: [Xen-devel] cpuidle causing Dom0 soft lockups
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 11 Feb 2010 17:01:46 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 11 Feb 2010 09:02:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B7425E1020000780002F038@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqrKL5XMvOgGIEASc6ZgwLFolAXtQAEyY/W
Thread-topic: [Xen-devel] cpuidle causing Dom0 soft lockups
User-agent: Microsoft-Entourage/12.23.0.091001
On 11/02/2010 14:44, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

> Other than with the global processed_system_time,
> the per-CPU one may not get increased even if delta_cpu was close
> to 3*NS_PER_TICK, due to the stolen/blocked accounting. Probably
> this was not a problem so far because no code outside of
> timer_interrupt() read this value - Keir, since I think you wrote that
> logic originally, any word on this?

What you say is true, as clearly it is currently implemented that way almost
by design. I'm lost in the intricacies of your current discussion though, so
not sure exactly why it's a problem, and how we should fix it?

 Thanks,
 Keir



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