From: Keir Fraser Subject: Re: Xen 3.4.1 NUMA support Date: Mon, 09 Nov 2009 12:40:15 +0000 Message-ID: References: <4AF800AD.3070407@ts.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AF800AD.3070407@ts.fujitsu.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: Juergen Gross , George Dunlap Cc: Dan Magenheimer , "xen-devel@lists.xensource.com" , Papagiannis Anastasios List-Id: xen-devel@lists.xenproject.org On 09/11/2009 11:44, "Juergen Gross" wrote: > NUMA was a topic I wanted to look at as soon as cpupools are officially > accepted. Keir wanted to propose a way to get rid of the function > continue_hypercall_on_cpu() which was causing most of the stuff leading > to the objection of cpupools. > I guess Keir had some higher priority jobs. :-) Well, I forgot about it. I think the plan was to perhaps keep something like continue_hypercall_on_cpu(), but not need to actually run the vcpu itself 'over there' but instead schedule a tasklet or somesuch, and sleep on its completion. That would get rid of the skanky affinity hacks you had to do to support continue_hypercall_on_cpu(). I'll have a look back at what we discussed. -- Keir