From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lcm72-0004Sr-Vt for qemu-devel@nongnu.org; Thu, 26 Feb 2009 14:41:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lcm71-0004Qa-AT for qemu-devel@nongnu.org; Thu, 26 Feb 2009 14:41:40 -0500 Received: from [199.232.76.173] (port=47622 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lcm71-0004QP-18 for qemu-devel@nongnu.org; Thu, 26 Feb 2009 14:41:39 -0500 Received: from mail-bw0-f171.google.com ([209.85.218.171]:40752) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lcm70-0002St-7w for qemu-devel@nongnu.org; Thu, 26 Feb 2009 14:41:38 -0500 Received: by bwz19 with SMTP id 19so627004bwz.34 for ; Thu, 26 Feb 2009 11:41:36 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20090226093640.GA413@shareable.org> References: <20090226093640.GA413@shareable.org> Date: Thu, 26 Feb 2009 21:41:36 +0200 Message-ID: Subject: Re: [Qemu-devel] Machine description, an alternativ using XML From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 2/26/09, Jamie Lokier wrote: > Torbj=C3=B6rn Andersson wrote: > > > > > > > > > > > > > > > > > > > > .... > > > > > > > > > > > > > > > Why so verbose? > > > > > 8192 > > > > > > > 0xc0010000 > > > > > > I know you are looking at a solution based on FDT. My belief is that t= he XML > > solution is more flexible, but I admit that I know very little about F= DT. > > Further, I believe that one can create FDTs, from the XML machine > > definitions, in runtime and pass them to the target-os if required. > > > > The strong point with the XML solution is that it is very suitable for > > modeling embedded systems where lots of GPIOs, interrupts, dma-channel= s, > > i2c, spi, i2s/pcm etc. > > > Isn't FDT capable of that too? > > > > I know that this is will result in a large patch set but I think the F= DT is > > equally big. Further I believe we can have both schemes in QEMU in par= allel, > > if necessary. > > > If the schemes are equivalently powerful, you can have a converter > which sits outside QEMU. No need to implement both inside QEMU. > People do this already, converting config files to QEMU command line > options. > > Fwiw, Microsoft Virtual PC uses an XML file to describe the machine > and it makes sense to me. > > Here's an example from a real VPC machine. Hmm, maybe it's a bit long. > Is the equivalent FDT any clearer or shorter, though? > > -- Jamie > > > > > > > 2.0 > > > true > > > > > 512 > > > > 1 > > > 123412341234123412341234123412= 34 > Marvell Yukon 88E8056 PCI-E= Gigabit Ethernet Controller > > 000123456789 > > > > 8 > > > > > 2 > > \\srv\Develop\Softw= are\MS SQL Eval\SQLEVAL.ISO > > > > > > > 1 > > C:\Documents and Se= ttings\test\My Documents\My Virtual Machines\test\test Hard Disk.vhd > .\test Hard Disk.vh= d > > > > > > > > > > > Virtual PC 2007 > 0001.0000.0000 > > > > > > > > > > true > > > false > 0 > > > false > > > > > 8886-9141-1653-9060-4025-7= 842-65 > > {125BDA48-420C-446E-AA48-9B5976322= 29C} > 8886-9141-1653-9060-4025-= 7842-65 > > 8886-9141-1653-9060-4025-7842-= 65 > 8886-9141-1653-9060-4025-7= 842-65 > > 00004000F0223F8002FFFF2F00FF3F1000003F00= 000000000031004C070707070666FFFF208580FF01000000200C01800CF4000000000000000= 00000000000901A32E24A580050E999E62401002784004A2080240000000000085AACFE1032= 547698BAE400000000000003000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000 > 42004800120002290408 > > > > > > true > > > > 013803 > > 5.02.3790 > Microsoft Windows Server 2= 003 > Service Pack 2 > Windows Server 2003 > Server > > > > > > > 6.0.156.0 > Microsoft Virtual PC 2007 > > > 6.0.156.0 > Microsoft Virtual PC 2007 > > > > > true > > 4 > false > > > true > > > true > > > true > > > 0 > true > > > > > true > > > > > 2 > > > > false > false > true > > > 6 > > > > true > > > OK, so now we have: 1 - Fabrice's original proposal 2 - Paul's FDT based work 3 - Mark's FDT based work 4 - Torbj=C3=B6rn's XML based configuration 5 - Microsoft XML configuration Actually this M$ version could be interesting for compatibility reasons.