From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [vNUMA v2][PATCH 2/8] public interface Date: Tue, 3 Aug 2010 16:52:54 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" 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: Dulloor Cc: Andre Przywara , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 03/08/2010 16:43, "Dulloor" wrote: >> I would expect guest would see nodes 0 to nr_vnodes-1, and the mnode_id >> could go away. > mnode_id maps the vnode to a particular physical node. This will be > used by balloon driver in > the VMs when the structure is passed as NUMA enlightenment to PVs and > PV on HVMs. > I have a patch ready for that (once we are done with this series). So what happens when the guest is migrated to another system with different physical node ids? Is that never to be supported? I'm not sure why you wouldn't hide the vnode-to-mnode translation in the hypervisor. -- Keir