From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42382) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RuoIU-0000IR-19 for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:53:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RuoIP-0004af-5o for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:53:37 -0500 Received: from mail-pz0-f45.google.com ([209.85.210.45]:38954) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RuoIO-0004aS-Vz for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:53:33 -0500 Received: by dadp14 with SMTP id p14so7776570dad.4 for ; Tue, 07 Feb 2012 08:53:31 -0800 (PST) Message-ID: <4F315704.1040306@codemonkey.ws> Date: Tue, 07 Feb 2012 10:53:24 -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> <4F31544B.8040808@suse.de> In-Reply-To: <4F31544B.8040808@suse.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-15?Q?Andreas_F=E4rber?= Cc: Paolo Bonzini , Developers qemu-devel , KVM devel mailing list , quintela@redhat.com On 02/07/2012 10:41 AM, Andreas Färber wrote: > Am 07.02.2012 16:21, schrieb Paolo Bonzini: >> BTW, I would like to change /i440fx to /devices/i440fx, so that we will >> have clean namespaces: >> >> /block >> ... >> /chardev >> ... >> /clocks >> ... >> /devices >> /peripheral >> ... # named devices created with -device >> /peripheral-anon >> /child[...] # unnamed devices created with -device >> /default >> /child[...] # created with qdev_create > > I don't like that, I prefer /i440fx over /devices/i440fx. I don't mind > the other root-level nodes though. Let's try Paolo's cleanup for now. I am worried about proliferation of things in the root hierarchy and the nice advantage of having /devices is that we can work towards making our build infrastructure roughly match our hierarchy. Since 1.1 is unstable for QOM, we can always change it later. > > For PC-style machines I'd expect board-level stuff like the CPUs to > appear directly under /. That would roughly correspond to the > OpenFirmware device tree then. I think devices trees are a bad example that should not be emulated. Regards, Anthony Liguori