From: Keir Fraser Subject: Re: Xen 3.4.1 NUMA support Date: Fri, 13 Nov 2009 16:02:38 +0000 Message-ID: References: <4FA716B1526C7C4DB0375C6DADBC4EA342A71C17D7@LONPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA342A71C17D7@LONPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt , Andre Przywara , George Dunlap Cc: Dan Magenheimer , "xen-devel@lists.xensource.com" , Papagiannis Anastasios List-Id: xen-devel@lists.xenproject.org On 13/11/2009 15:40, "Ian Pratt" wrote: >> Even better would be to have pCPUs addressable and listable explicitly as >> dotted tuples. That can be implemented entirely within the toolstack, and >> could even allow wildcarding of tuple components to efficiently express >> cpumasks. > > Yes, I'd certainly like to see the toolstack support dotted tuple notation. > > However, I just don't trust the toolstack to get this right unless xen has > already set it up nicely for it with a sensible enumeration and defined > sockets-per-node, cores-per-socket and threads-per-core parameters. Xen should > provide a clean interface to the toolstack in this respect. Xen provides a topology-interrogation hypercall which should suffice for tools to build up a {node,socket,core,thread}<->cpuid mapping table. -- Keir