From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=37090 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PzSHo-0004dL-FC for qemu-devel@nongnu.org; Tue, 15 Mar 2011 07:19:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PzSHm-0002RI-EP for qemu-devel@nongnu.org; Tue, 15 Mar 2011 07:19:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:31591) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PzSHm-0002R2-5y for qemu-devel@nongnu.org; Tue, 15 Mar 2011 07:19:34 -0400 Message-ID: <4D7F4BBC.6010509@redhat.com> Date: Tue, 15 Mar 2011 12:21:32 +0100 From: Kevin Wolf MIME-Version: 1.0 References: <4D7E5507.8010205@codemonkey.ws> In-Reply-To: <4D7E5507.8010205@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [RFC] QCFG: a new mechanism to replace QemuOpts and option handling List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Chris Wright , Stefan Hajnoczi , qemu-devel , Markus Armbruster , Adam Litke 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, are you going to store a list of all -blockdev options used? And why isn't it a QLIST or something? Kevin