From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [Patch] avoid deadlock during console output
Date: Fri, 06 Mar 2009 09:11:57 +0000
Message-ID: <C5D6995D.4493%keir.fraser@eu.citrix.com>
References: <49B0E2F0.5060104@fujitsu-siemens.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <49B0E2F0.5060104@fujitsu-siemens.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Juergen Gross <juergen.gross@fujitsu-siemens.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 06/03/2009 08:46, "Juergen Gross" <juergen.gross@fujitsu-siemens.com>
wrote:

> to dump the schedulers run-queues. On my 4-core machine I need only about 5
> calls to stop the machine.
> 
> The attached patch solves the problem by avoiding sending the event in
> critical paths.

Ugly. Instead we can defer the dom0 notification to a tasklet. I'll make a
patch for that myself.

 Thanks,
 Keir