From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=39343 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q0R2z-000156-TP
	for qemu-devel@nongnu.org; Fri, 18 Mar 2011 00:12:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q0R2y-0001tG-LI
	for qemu-devel@nongnu.org; Fri, 18 Mar 2011 00:12:21 -0400
Received: from mail-iw0-f173.google.com ([209.85.214.173]:64559)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q0R2y-0001tA-H4
	for qemu-devel@nongnu.org; Fri, 18 Mar 2011 00:12:20 -0400
Received: by iwl42 with SMTP id 42so4046994iwl.4
	for <qemu-devel@nongnu.org>; Thu, 17 Mar 2011 21:12:20 -0700 (PDT)
Message-ID: <4D82DB92.2090206@codemonkey.ws>
Date: Thu, 17 Mar 2011 23:12:02 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [RFC] QCFG: a new mechanism to replace QemuOpts
	and option handling
References: <4D7E5507.8010205@codemonkey.ws>
	<4D7F4BBC.6010509@redhat.com>	<4D7F6BAB.8040709@codemonkey.ws>
	<4D7F6EF3.2010504@redhat.com>
	<m339ml4vkp.fsf@blackfin.pond.sub.org>
In-Reply-To: <m339ml4vkp.fsf@blackfin.pond.sub.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Chris Wright <chrisw@redhat.com>, Adam Litke <agl@us.ibm.com>, qemu-devel <qemu-devel@nongnu.org>, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>

On 03/17/2011 10:26 AM, Markus Armbruster wrote:
> Kevin Wolf<kwolf@redhat.com>  writes:
>
>> Am 15.03.2011 14:37, schrieb Anthony Liguori:
>>> On 03/15/2011 06:21 AM, Kevin Wolf wrote:
>>>> Am 14.03.2011 18:48, schrieb Anthony Liguori:
>>>>> I've got a spec written up at http://wiki.qemu.org/Features/QCFG.
>>>>> Initial code is in my QAPI tree.
>>>> One question about a small detail on this wiki page:
>>>>
>>>>> typedef struct BlockdevConfig {
>>>>>       char * file;
>>>>>       struct BlockdevConfig * backing_file;
>>>>>
>>>>>       struct BlockdevConfig * next;
>>>>> } BlockdevConfig;
>>>> What is the 'next' pointer used for,
>>> This is a standard part of QAPI.  All types get a next pointer added
>>> such that we can support lists of complex types.
>> Only a single list for each object.
> Don't even think of trees.  Yuck.

Sorry, don't fully understand.  The above data structure is a tree.

I haven't looked yet at converting the code generator to use the 
qemu-queue structures.  I'm not sure I agree it's the right thing to do 
but I don't think it's all that hard.

Regards,

Anthony Liguori