From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IE8Ze-0003S3-Nc for qemu-devel@nongnu.org; Thu, 26 Jul 2007 15:00:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IE8Zd-0003Rj-D3 for qemu-devel@nongnu.org; Thu, 26 Jul 2007 15:00:34 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IE8Zd-0003Rg-58 for qemu-devel@nongnu.org; Thu, 26 Jul 2007 15:00:33 -0400 Received: from ug-out-1314.google.com ([66.249.92.173]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IE8Zc-0005qG-N0 for qemu-devel@nongnu.org; Thu, 26 Jul 2007 15:00:32 -0400 Received: by ug-out-1314.google.com with SMTP id m2so554038uge for ; Thu, 26 Jul 2007 12:00:31 -0700 (PDT) Message-ID: Date: Thu, 26 Jul 2007 21:00:31 +0200 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] QEmu as a Device Software Optimization tool In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <001201c7cade$8118b8e0$ba00a8c0@kone> 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 Hi, On 26/07/07, Paul Borman wrote: > QEmu Target Configuration - I would like to define a configuration > file syntax (I cannot help but think back to my BSDi days and the BSD/ > OS kernel configuration file) that would define the hardware from the > outside. Device drivers would either need to be already linked in, > or be able to be dynamically loaded. I would expect that things such > as the memory map, type of interrupt controller, the various devices > along with their io port and memory addresses and interrupts would be > defined here. Again, this would not replace the current system, but > would essentially be a new init module. I do not want to see any > working configurations break. There is some interesting work being done on a similar project by Paul Sokolovsky for his and Maria Zabolotnaya's Google Summer Of Project. In their approach machine descriptions (but not only) are written in python, which lets you hope that they can have a simple syntax, practically like a config file, if desired, or a much more powerful one, so it seems to be a better idea than plain config files. Personally though I don't see much benefit to simple syntax config files over C files, that are being used now. Regards