From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] KVM call minutes for Feb 8 Date: Wed, 09 Feb 2011 20:59:06 +0100 Message-ID: <4D52F20A.7070009@codemonkey.ws> References: <20110208155557.GM6198@x200.localdomain> <4D51B1C9.3080507@codemonkey.ws> <4D526D0D.9020507@codemonkey.ws> <4D52A86A.1030407@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris Wright , Markus Armbruster , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Blue Swirl Return-path: Received: from mail-fx0-f46.google.com ([209.85.161.46]:41964 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754055Ab1BIT7o (ORCPT ); Wed, 9 Feb 2011 14:59:44 -0500 Received: by fxm20 with SMTP id 20so591966fxm.19 for ; Wed, 09 Feb 2011 11:59:43 -0800 (PST) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 02/09/2011 06:48 PM, Blue Swirl wrote: >> ISASerialState dev; >> >> isa_serial_init(&dev, 0, 0x274, 0x07, NULL, NULL); >> > Do you mean that there should be a generic way of doing that, like > sysbus_create_varargs() for qdev, or just add inline functions which > hide qdev property setup? > > I still think that FDT should be used in the future. That would > require that the properties can be set up mechanically, and I don't > see how your proposal would help that. > Yeah, I don't think that is a good idea anymore. I think this is part of why we're having so many problems with qdev. While (most?) hardware hierarchies can be represented by device tree syntax, not all valid device trees correspond to interface and/or useful hardware hierarchies. We want to have an interface to create large chunks of hardware (like an i440fx) which then results in a significant portion of a device tree. Regards, Anthony Liguori