From: Keir Fraser Subject: Re: Xen 3.4.1 NUMA support Date: Fri, 13 Nov 2009 15:27:28 +0000 Message-ID: References: <4FA716B1526C7C4DB0375C6DADBC4EA342A71C17C9@LONPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA342A71C17C9@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 14:29, "Ian Pratt" wrote: > I'd really like to see us enumerate pCPUs in a sensible order so that it's > easier to see the topology. It should be nodes.sockets.cores{.threads}, > leaving gaps for missing execution units due to hot plug or non power of two > packing. > Right now we're inconsistent in the enumeration order depending on how the > BIOS has set things up. It would be great if someone could volunteer to fix > this... 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. -- Keir