From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ross Philipson <ross.philipson@citrix.com>
Subject: Re: passing smbios table from qemu
Date: Tue, 14 Jan 2014 10:21:54 -0500
Message-ID: <52D55612.8060501@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>
	<52D058F3.5080504@citrix.com>
	<1389608732.13654.5.camel@kazak.uk.xensource.com>
	<21203.52907.856721.125370@mariner.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <21203.52907.856721.125370@mariner.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, "Zhang,
	Eniac" <eniac-xw.zhang@hp.com>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 01/13/2014 06:31 AM, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] passing smbios table from qemu"):
>> On Fri, 2014-01-10 at 15:32 -0500, Ross Philipson wrote:
>>> On 01/10/2014 10:03 AM, Ian Campbell wrote:
>>>> 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.
>>
>> I think that (aux functionality) was the intention -- the fact that it
>> is all parsing stuff right now is just a coincidence.

Ok then libxlu sounds like a reasonable place for this. I will submit a 
patch.

>>
>> (Ian J: right?)
>
> Yes, that's right.
>
> Thanks,
> Ian.
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3658/6999 - Release Date: 01/13/14
>


-- 
Ross Philipson