From: Keir Fraser Subject: Re: [PATCH] numa: fix problems with memory-less nodes Date: Wed, 13 Jan 2010 10:02:30 +0000 Message-ID: References: <4B4D9582.5010806@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B4D9582.5010806@amd.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: Andre Przywara Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 13/01/2010 09:42, "Andre Przywara" wrote: > node_to_cpu : node0:0-5,24-35 > node1:6-11 > node2:12-17 > node3:18-23 > node4:no cpus > node5:no cpus > node_to_memory : node0:14267 > node1:8167 > node2:16335 > node3:8167 > node4:0 > node5:0 To be clear: I certainly agree that node_to_cpu[4,5] should list the CPUs that are present, even if the nodes are memory-less. But you tell me how 20762 has changed this behaviour. If it was changed by one of Intel's slightly earlier changesets (which is possible) I'm happy to see it changed back. The new node_to_cpu[] behaviour you are observing is obviously stupid, and I assume unintended. -- Keir