[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45D58D88.5020801@vmware.com>
Date: Fri, 16 Feb 2007 02:55:04 -0800
From: Zachary Amsden <zach@...are.com>
To: Keir Fraser <keir@...source.com>
CC: Jeremy Fitzhardinge <jeremy@...p.org>,
xen-devel@...ts.xensource.com, Andi Kleen <ak@....de>,
Dan Hecht <dhecht@...are.com>, linux-kernel@...r.kernel.org,
Chris Wright <chrisw@...s-sol.org>,
Ian Pratt <ian.pratt@...source.com>,
virtualization@...ts.osdl.org,
Andrew Morton <akpm@...ux-foundation.org>,
Steven Hand <steven.hand@...cam.ac.uk>
Subject: Re: [Xen-devel] Re: [patch 14/21] Xen-paravirt: Add XEN config options
and disable unsupported config options.
Keir Fraser wrote:
> On 16/2/07 10:19, "Zachary Amsden" <zach@...are.com> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists