From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: Re: [PATCH v5 17/24] libxl: build, check and pass vNUMA info to Xen for HVM guest Date: Fri, 13 Feb 2015 15:18:27 +0000 Message-ID: <20150213151827.GF13644@zion.uk.xensource.com> References: <1423770294-9779-1-git-send-email-wei.liu2@citrix.com> <1423770294-9779-18-git-send-email-wei.liu2@citrix.com> <21726.2151.839153.545182@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <21726.2151.839153.545182@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Wei Liu , ian.campbell@citrix.com, andrew.cooper3@citrix.com, dario.faggioli@citrix.com, xen-devel@lists.xen.org, JBeulich@suse.com, ufimtseva@gmail.com List-Id: xen-devel@lists.xenproject.org On Fri, Feb 13, 2015 at 02:21:27PM +0000, Ian Jackson wrote: > Wei Liu writes ("[PATCH v5 17/24] libxl: build, check and pass vNUMA info to Xen for HVM guest"): > > Transform user supplied vNUMA configuration into libxl internal > > representations then libxc representations. Check validity along the > > line. > > This is going to be a totally stupid question: but why are there three > representations here, rather than two ? > There are two. One is libxl and the other is libxc. > Is the libxc representation too annoying for use internally in libxl ? > Yes, because libxl's representation is consolidated so that it can be easily used by libxl's user while libxc doesn't actually care about all the fields in libxl's structure. Wei. > Ian.