From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] xen: explicitly create/destroy stop_machine
	workqueues outside suspend/resume region.
Date: Tue, 01 Dec 2009 14:50:25 -0800
Message-ID: <4B159DB1.1050709@goop.org>
References: <1259668035-8552-1-git-send-email-ian.campbell@citrix.com>
	<1259668035-8552-2-git-send-email-ian.campbell@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1259668035-8552-2-git-send-email-ian.campbell@citrix.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: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 12/01/09 03:47, Ian Campbell wrote:
> I have observed cases where the implicit stop_machine_destroy() done by
> stop_machine() hangs while destroying the workqueues, specifically in
> kthread_stop(). This seems to be because timer ticks are not restarted
> until after stop_machine() returns.
>   

Thanks for these - applied.

    J