From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gc9u5-0000En-4Y for qemu-devel@nongnu.org; Mon, 23 Oct 2006 20:12:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gc9u3-0000CN-2X for qemu-devel@nongnu.org; Mon, 23 Oct 2006 20:12:24 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gc9u2-0000CC-Py for qemu-devel@nongnu.org; Mon, 23 Oct 2006 20:12:22 -0400 Received: from [64.233.182.187] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gc9u2-0002gN-Df for qemu-devel@nongnu.org; Mon, 23 Oct 2006 20:12:22 -0400 Received: by nf-out-0910.google.com with SMTP id p46so398nfa for ; Mon, 23 Oct 2006 17:12:21 -0700 (PDT) Date: Tue, 24 Oct 2006 03:12:22 +0300 From: Paul Sokolovsky Message-ID: <796615070.20061024031222@gmail.com> Subject: Re[2]: [Qemu-devel] Config file support In-Reply-To: <200610232129.53615.paul@codesourcery.com> References: <200610221927.34528.paul@codesourcery.com> <200610231601.44583.rob@landley.net> <200610232129.53615.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: Paul Sokolovsky , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org Hello Paul, Monday, October 23, 2006, 11:29:52 PM, you wrote: > On Monday 23 October 2006 21:01, Rob Landley wrote: >> On Sunday 22 October 2006 2:27 pm, Paul Brook wrote: >> > I've been considering a machine config file for a while, but haven't come >> > up with a coherent way of representing everything yet. I'm glad this discussion was brought up on the list. And I'd like to also bring back another related issue - what about providing "plugin" system for device (chip) implementation, in addition to flexible-format machine config allowing to construct "virtual boards" out of them? >> >> Do you at least have a list of everything that needs to be represented? (I >> have a list but am fairly certain it's not complete.) > Not really. I guess a generic key/value pair is sufficient for most things > (base address, model number, etc). > The trickier cases are where devices refer to each other: PCI, usb, IRQ lines, > DMA channels, etc. ie. anything where the existing _init function returns a > value. > I guess you could use the same key/value mechanism, and allow the value to be > an "object". Yes, machine config apparently would be a hierarchical structure, with cross-references. And well, there's an industrial standard to represent that - XML. > The really OTT method is to embed a python interpreter or something and do the > machine init that way. I'm not seriously suggesting that though. Well, I guess, machine configuration really a declarative information, and XML should be enough. But it would be really nice to have Python bindings to implement device plugin, especially for "boring" hardware like, say, battery controllers. What about config like: > Paul -- Best regards, Paul mailto:pmiscml@gmail.com