From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7 Date: Tue, 07 Feb 2012 17:27:28 +0100 Message-ID: <4F3150F0.8060805@redhat.com> References: <87ehu7pxvf.fsf@elfo.elfo> <4F312AFC.6020908@suse.de> <4F312C8A.9080700@redhat.com> <4F313BA8.9070601@codemonkey.ws> <4F31417F.2000102@redhat.com> <4F315033.7060105@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: quintela@redhat.com, =?ISO-8859-15?Q?Andreas_F=E4rber?= , KVM devel mailing list , Developers qemu-devel To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:6587 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754525Ab2BGQ1f (ORCPT ); Tue, 7 Feb 2012 11:27:35 -0500 In-Reply-To: <4F315033.7060105@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On 02/07/2012 05:24 PM, Anthony Liguori wrote: >> I'm wary of all plans that require to go through all the code once. What about >> simply /devices/default/child[...] or something like that? > > The paths would be unstable, but maybe that's okay. I'd suggest > doing child[rand()] to avoid the appearance that these paths are in > any way shape or form stable. Sounds a bit inconvenient for humans (who in the end are those who debug things :)). >> BTW, I would like to change /i440fx to /devices/i440fx, so that we >> will have clean namespaces: >> >> /block >> /chardev >> /clocks >> /devices > > Yeah, this makes sense. By clocks, you mean things like rtc_clock, > vm_clock, etc? Not the omap clocks which happen to live in /clocks in > your series? No, I really meant the OMAP clocks. :) Basically if you have an abstract subclass TYPE_FOOS of TYPE_OBJECT, its instances would reside under /foos or something easily related to "foos". Paolo