From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:51469) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbV6k-0000y0-AZ for qemu-devel@nongnu.org; Fri, 16 Dec 2011 05:33:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RbV6e-0005Sk-Ou for qemu-devel@nongnu.org; Fri, 16 Dec 2011 05:33:42 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53111) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbV6e-0005RQ-II for qemu-devel@nongnu.org; Fri, 16 Dec 2011 05:33:36 -0500 Message-ID: <4EEB1F3B.8070302@redhat.com> Date: Fri, 16 Dec 2011 11:36:43 +0100 From: Kevin Wolf MIME-Version: 1.0 References: <1323721784-704-1-git-send-email-aliguori@us.ibm.com> <4EEA3813.80006@us.ibm.com> <4EEB1277.4070803@redhat.com> <4EEB1ABB.50204@redhat.com> In-Reply-To: <4EEB1ABB.50204@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 00/20] qom: dynamic properties and composition tree List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Peter Maydell , Anthony Liguori , Stefan Hajnoczi , Jan Kiszka , qemu-devel@nongnu.org, Luiz Capitulino , Markus Armbruster Am 16.12.2011 11:17, schrieb Paolo Bonzini: > On 12/16/2011 10:42 AM, Kevin Wolf wrote: >>>> >>>> Applied. >>>> >>>> Regards, >>>> >>>> Anthony Liguori >> So you pushed this with qdev_property_add_child() calls spread all over >> the place instead of being treated like other properties?:-( > > I think actually this is not the biggest problem. child properties are > dynamic, and it's not a problem IMO if they are created like that. That they are added in an init function is an indicator that they aren't really dynamic. Some of them are conditional, some aren't. For those which are, I think having a child property that can be NULL could be reasonable. In the end you want to have this kind of things configurable via QOM instead of hard-coded in the devices, right? > I don't like that _link_ properties are spread all over the place > instead of being treated like other properties. Link properties are > static, and PROP_PTR properties could often be converted to links. Yes, links too. Kevin