From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: Cpu pools discussion Date: Tue, 28 Jul 2009 12:19:14 +0200 Message-ID: <4A6ED0A2.3010108@ts.fujitsu.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 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: George Dunlap , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > On 28/07/2009 06:40, "Juergen Gross" wrote: > >> BTW: continue_hypercall_on_cpu() exists on x86 only and it isn't really much >> better than my usage of it: >> - remember old pinning state of current vcpu >> - pin it temporarily to the cpu it should continue on >> - continue the hypercall >> - remove temporary pinning >> - re-establish old pinning (if any) >> Pretty much the same as my solution above ;-) > > If your solution locks the pinning, as we do already, so that it cannot be > changed while the continue_hypercall_on_cpu() is running, then that is fine. > If it's not locked then it's not safe. Locking in my solution should be okay. Juergen -- Juergen Gross Principal Developer Operating Systems TSP ES&S SWE OS6 Telephone: +49 (0) 89 636 47950 Fujitsu Technolgy Solutions e-mail: juergen.gross@ts.fujitsu.com Otto-Hahn-Ring 6 Internet: ts.fujitsu.com D-81739 Muenchen Company details: ts.fujitsu.com/imprint.html