From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: Re: [patch 14/21] Xen-paravirt: Add XEN config options and disable unsupported config options. Date: Fri, 16 Feb 2007 02:55:04 -0800 Message-ID: <45D58D88.5020801@vmware.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Ian Pratt , Dan Hecht , linux-kernel@vger.kernel.org, Chris Wright , Andi Kleen , virtualization@lists.osdl.org, Andrew Morton , Steven Hand List-Id: virtualization@lists.linuxfoundation.org Keir Fraser wrote: > On 16/2/07 10:19, "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? >> > > It ensures that no (non-stopmachine) threads are running on any of the other > CPUs, but it doesn't guarantee that all threads are at any form of quiescent > point. They can certainly have private references to machine addresses. > > Otherwise, what would be the point of the process freezer? :-) > Yeah, I was over-hoping on that one. At least thought it was worth suggesting as a starting point. I had similar issues considering loading VMI as a module at runtime. Zach