From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M4tvz-0007VP-0E for qemu-devel@nongnu.org; Fri, 15 May 2009 05:42:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M4tvu-0007TW-0c for qemu-devel@nongnu.org; Fri, 15 May 2009 05:42:30 -0400 Received: from [199.232.76.173] (port=35546 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M4tvt-0007TR-SR for qemu-devel@nongnu.org; Fri, 15 May 2009 05:42:25 -0400 Received: from mx2.redhat.com ([66.187.237.31]:54593) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M4tvt-0004Rh-Gs for qemu-devel@nongnu.org; Fri, 15 May 2009 05:42:25 -0400 Message-ID: <4A0D3885.1010701@redhat.com> Date: Fri, 15 May 2009 11:40:21 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] New device API References: <200905142239.18358.paul@codesourcery.com> In-Reply-To: <200905142239.18358.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org On 05/14/09 23:39, Paul Brook wrote: > I've just pushed out changes implementing a new device API. > > This is based on my previous RFC[1], but with a few changes. The main one > being increased used of proxies/wrappers to implement common bus > functionality. For example there are frameworks for PCI, "ISA"[1] and I2C > devices all built on top of a common core. I think we should also have a generic BusState with a name and a list of devices attached (maybe more). Then have "BusState *bus" instead of "void *bus". Then you can actually walk the device tree in common code, for example have a "info devtree" monitor command printing all devices of the machine. cheers, Gerd