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] Diagnose stuff

To: Juergen Gross <juergen.gross@xxxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Diagnose stuff
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 26 Mar 2009 07:14:53 +0000
Cc:
Delivery-date: Thu, 26 Mar 2009 00:15:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49C9EA48.2080907@xxxxxxxxxxxxxxxxxxx>
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: AcmtIzNzZ8lRnUmGRtWQMFvclK3xigAv1uIK
Thread-topic: [Xen-devel] Diagnose stuff
User-agent: Microsoft-Entourage/12.15.0.081119
On 25/03/2009 08:24, "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxxxxxxx>
wrote:

> while implementing cpupool support in XEN I had to track down some issues
> with deadlocks. Is there any interest in patches for the following?
> 
> - compile time switchable spinlock timeout detection

NMI watchdog support effectively gets us this, and more general deadlock
detection. Just put 'watchdog' on Xen's command line.

> - printout of state of ALL cpus to console in case of hypervisor crash

Not sure how useful this would be really for most crashes. Probably we don't
want it.

> - some enhancements in lock handling to reduce (potential) latency:
>   Today in *lock_irq and *lock_irqsave interrupts are disabled and then
>   spinning is started. If the lock is not obtained, enabling and disabling of
>   IRQs in the spinloop would block IRQs as short as possible.

Could do. I don't think our IRQ locks are very contended, but equally I
suppose the patch is only a few lines.

 -- Keir



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

<Prev in Thread] Current Thread [Next in Thread>