From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M9g4p-0001tx-K6 for qemu-devel@nongnu.org; Thu, 28 May 2009 09:55:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M9g4k-0001su-K0 for qemu-devel@nongnu.org; Thu, 28 May 2009 09:55:23 -0400 Received: from [199.232.76.173] (port=50883 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M9g4k-0001sr-Fg for qemu-devel@nongnu.org; Thu, 28 May 2009 09:55:18 -0400 Received: from mx2.redhat.com ([66.187.237.31]:55712) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M9g4j-00030i-DK for qemu-devel@nongnu.org; Thu, 28 May 2009 09:55:17 -0400 Subject: Re: [Qemu-devel] [RFC] New device API References: <200905051231.09759.paul@codesourcery.com> <20090508052755.GA13230@amt.cnet> From: Markus Armbruster Date: Thu, 28 May 2009 15:53:11 +0200 In-Reply-To: <20090508052755.GA13230@amt.cnet> (Marcelo Tosatti's message of "Fri\, 8 May 2009 02\:27\:55 -0300") Message-ID: <87prdte3lk.fsf@pike.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcelo Tosatti Cc: Paul Brook , qemu-devel@nongnu.org Marcelo Tosatti writes: [...] > Markus should have more substantial comments (he's on vacation > this week). The tree driven machine initialization introduces some > complications (such as parent_bus->child device dependencies) while > handling a lot of the problems you are ignoring (eg the ->config method > is responsible for linking host device -> emulated device information, > etc). The patch looks okay for what it attempts to do. I don't think rehashing the differences in scope to my prototype would do much good. It'll be interesting to see how the API will evolve to accommodate data-driven machine building. What's the plan for getting there?