From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ross Philipson Subject: Re: passing smbios table from qemu Date: Fri, 10 Jan 2014 15:32:51 -0500 Message-ID: <52D058F3.5080504@citrix.com> References: <3B22ECA2D19A3D408C83F4F15A9CB7D45075EA57@G4W3221.americas.hpqcorp.net> <1389102962.12612.19.camel@kazak.uk.xensource.com> <92B37F2487AE0841841737618F25AC1A1918AABE@FTLPEX01CL03.citrite.net> <1389261984.27473.46.camel@kazak.uk.xensource.com> <52CEB663.4070609@citrix.com> <20140109190049.GB17806@pegasus.dumpdata.com> <1389349212.19142.21.camel@kazak.uk.xensource.com> <52D002D6.7090306@citrix.com> <1389366233.19142.60.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1389366233.19142.60.camel@kazak.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 Campbell Cc: Ian Jackson , "xen-devel@lists.xen.org" , "Zhang, Eniac" List-Id: xen-devel@lists.xenproject.org On 01/10/2014 10:03 AM, Ian Campbell wrote: > On Fri, 2014-01-10 at 09:25 -0500, Ross Philipson wrote: >> So I guess that is the question: where to put it? Should it be merged >> into another lib or be brought in as a separate lib or utility? > > I guess the choices are libxc, libxl, libxlutils or an entirely new lib? > > At what level would we expect this to be used? Would it be internal to > e.g. libxl (in which case libxc or libxl would be appropriate) or would > toolstacks be expected to use it and pass the result to libxl? If that > is the case then libxc is inappropriate (users of libxl are not supposed > to have to deal with libxc directly). I don't think it would be internal to libxl. I think it would be used the second way you mention; toolstacks would use it and pass the results. The exact way it is used would be implementation specific. Files might need to be generated once, on every boot, before vms are started, etc. I did not think it belonged in either libxl/xc. > > Fitting in with libxl proper would require the API to look a certain way > (take a context etc), so perhaps libxlu would be more appropriate, > alongside the disk syntax parser etc? Possibly. I looked at that back then (and today again) and it seemed to all be related to parsing things into XLU_Config objects. I guess I did not have a good feel for what libxlu was supposed to be. If it is supposed to be a generic library of auxiliary toolstack functionality then I think it would be a good place. Thanks Ross > > Ian. > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2014.0.4259 / Virus Database: 3658/6991 - Release Date: 01/10/14 >