From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: Re: [patch 14/21] Xen-paravirt: Add XEN config options and disable unsupported config options. Date: Sat, 17 Feb 2007 15:04:35 +1100 Message-ID: <1171685075.18876.21.camel@localhost.localdomain> References: <45D58531.4010808@vmware.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45D58531.4010808@vmware.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Zachary Amsden Cc: xen-devel@lists.xensource.com, virtualization@lists.osdl.org, Steven Hand , linux-kernel@vger.kernel.org, Chris Wright , Ian Pratt , Andrew Morton , Keir Fraser , Ingo Molnar , Andi Kleen List-Id: virtualization@lists.linuxfoundation.org On Fri, 2007-02-16 at 02:19 -0800, Zachary Amsden wrote: > Doesn't stop_machine_run already take care of getting you out of all > kernel threads? So you can only be sleeping, not preempted, in which > case, this might not be an issue? No, stop_machine only protects against preempt-disabled regions. I thought about making that particularly hammer bigger, but noone had needed it yet. It would simply require a runtime way of disabling further preemption and flushing preempted threads (AFAICT there can be no deadlock issues with this). Rusty.