Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MF999-000787-Or for qemu-devel@nongnu.org; Fri, 12 Jun 2009 11:58:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MF993-00077P-NF for qemu-devel@nongnu.org; Fri, 12 Jun 2009 11:58:26 -0400 Received: from [199.232.76.173] (port=45941 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MF993-00077L-DJ for qemu-devel@nongnu.org; Fri, 12 Jun 2009 11:58:21 -0400 Received: from mx2.redhat.com ([66.187.237.31]:44913) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MF991-0004Y4-RK for qemu-devel@nongnu.org; Fri, 12 Jun 2009 11:58:21 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n5CFwEAc002290 for ; Fri, 12 Jun 2009 11:58:14 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n5CFwD4G027397 for ; Fri, 12 Jun 2009 11:58:13 -0400 Received: from pike.pond.sub.org (vpn-10-124.str.redhat.com [10.32.10.124]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n5CFwC7M031881 for ; Fri, 12 Jun 2009 11:58:12 -0400 Subject: Re: [Qemu-devel] [PATCH 0/4] Machine config files References: <20090610173803.4674.82538.stgit@wren.home> <878wjx374h.fsf@pike.pond.sub.org> <4A3269C3.3050307@redhat.com> From: Markus Armbruster Date: Fri, 12 Jun 2009 17:58:11 +0200 In-Reply-To: <4A3269C3.3050307@redhat.com> (Gerd Hoffmann's message of "Fri\, 12 Jun 2009 16\:44\:19 +0200") Message-ID: <877hzhxx4c.fsf@pike.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Gerd Hoffmann writes: > On 06/12/09 15:37, Markus Armbruster wrote: >> It can be compiled from source with dtc, which doesn't seem to be >> included in the patch series. The language accepted by dtc is pretty >> low-level: it talks NUL-terminates strings, byte strings and arrays of >> "cells" (32 bit integers). > > [ a bunch of examples snipped ] > >> Is that really what we want for a configuration file? > > I do see a point in using fdt as qemu-internal representation. I was talking about configuration file usability. Internal representation is a different matter. > ppc > needs it anyway. Could be generated from whatever internal representation we use. > It is also a nice way to store the guest > configuration for save/load and migration, you can just send the blob > over the wire. And we can hide the details such as cells behind some > nifty helper functions. I agree we need the tree flattened to send it to disk or over the wire. Keeping it flattened all the time could make certain tree editing jobs more cumbersome. We'll see. > Qemu users should not be required to be fdt experts though. We need > another, more user-friendly interface to configure virtual machines. Yup. [...]