From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42157) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RunzW-0004Gk-6L for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:34:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RunzM-0000Sb-BP for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:34:02 -0500 Received: from mail-pw0-f45.google.com ([209.85.160.45]:41691) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RunzM-0000SP-6c for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:33:52 -0500 Received: by pbaa11 with SMTP id a11so8063410pba.4 for ; Tue, 07 Feb 2012 08:33:51 -0800 (PST) Message-ID: <4F315268.8030608@codemonkey.ws> Date: Tue, 07 Feb 2012 10:33:44 -0600 From: Anthony Liguori MIME-Version: 1.0 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> <4F3150F0.8060805@redhat.com> In-Reply-To: <4F3150F0.8060805@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: quintela@redhat.com, Developers qemu-devel , KVM devel mailing list , =?ISO-8859-1?Q?Andreas?= =?ISO-8859-1?Q?_F=E4rber?= On 02/07/2012 10:27 AM, Paolo Bonzini wrote: > 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 > :)). There are tons of human readable paths to a single object so I don't think it's a problem. But no big deal with way since /devices/default should go away anyway. > >>> 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". Hrm, I don't like that very much. OMAP clocks are devices. Don't they belong in the devices hierarchy under the omap-clocks branch? The fact that they aren't DeviceState's is because DeviceState is a pile of cruft. Perhaps we should introduce a more streamlined Device base class and rename DeviceState to LegacyDevice or something like that. Regards, Anthony Liguori > > Paolo >