From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lccfe-00034p-Jd for qemu-devel@nongnu.org; Thu, 26 Feb 2009 04:36:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lccfc-00034S-Sh for qemu-devel@nongnu.org; Thu, 26 Feb 2009 04:36:46 -0500 Received: from [199.232.76.173] (port=45327 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lccfc-00034H-K0 for qemu-devel@nongnu.org; Thu, 26 Feb 2009 04:36:44 -0500 Received: from mail2.shareable.org ([80.68.89.115]:54653) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Lccfb-0008QN-MA for qemu-devel@nongnu.org; Thu, 26 Feb 2009 04:36:44 -0500 Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from ) id 1LccfY-0000EW-Lw for qemu-devel@nongnu.org; Thu, 26 Feb 2009 09:36:40 +0000 Date: Thu, 26 Feb 2009 09:36:40 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] Machine description, an alternativ using XML Message-ID: <20090226093640.GA413@shareable.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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 Torbjörn Andersson wrote: > > > > > > > > > > .... > > > > > > Why so verbose? 8192 0xc0010000 > I know you are looking at a solution based on FDT. My belief is that the XML > solution is more flexible, but I admit that I know very little about FDT. > 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-channels, > 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 FDT is > equally big. Further I believe we can have both schemes in QEMU in parallel, > 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 12341234123412341234123412341234 Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller 000123456789 8 2 \\srv\Develop\Software\MS SQL Eval\SQLEVAL.ISO 1 C:\Documents and Settings\test\My Documents\My Virtual Machines\test\test Hard Disk.vhd .\test Hard Disk.vhd Virtual PC 2007 0001.0000.0000 true false 0 false 8886-9141-1653-9060-4025-7842-65 {125BDA48-420C-446E-AA48-9B597632229C} 8886-9141-1653-9060-4025-7842-65 8886-9141-1653-9060-4025-7842-65 8886-9141-1653-9060-4025-7842-65 00004000F0223F8002FFFF2F00FF3F1000003F00000000000031004C070707070666FFFF208580FF01000000200C01800CF400000000000000000000000000901A32E24A580050E999E62401002784004A2080240000000000085AACFE1032547698BAE400000000000003000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 42004800120002290408 true 013803 5.02.3790 Microsoft Windows Server 2003 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