From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:45726)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1Ruo9R-0001Qb-76
	for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:44:21 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1Ruo9M-0002qB-Oj
	for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:44:17 -0500
Received: from cantor2.suse.de ([195.135.220.15]:47741 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1Ruo9M-0002pp-K9
	for qemu-devel@nongnu.org; Tue, 07 Feb 2012 11:44:12 -0500
Message-ID: <4F31544B.8040808@suse.de>
Date: Tue, 07 Feb 2012 17:41:47 +0100
From: =?ISO-8859-15?Q?Andreas_F=E4rber?= <afaerber@suse.de>
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>
In-Reply-To: <4F31417F.2000102@redhat.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: quintela@redhat.com, Developers qemu-devel <qemu-devel@nongnu.org>, KVM devel mailing list <kvm@vger.kernel.org>

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:
>=20
> /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.

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. For embedded devices with SoCs I expect
them to show up as child<>s of the SoC, but definitely not under some
artificial /cpus.

Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe=
rg