From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55368) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R3wnq-0007vW-CS for qemu-devel@nongnu.org; Wed, 14 Sep 2011 17:15:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R3wno-00071R-Rw for qemu-devel@nongnu.org; Wed, 14 Sep 2011 17:15:30 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:45474) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R3wno-00071M-GM for qemu-devel@nongnu.org; Wed, 14 Sep 2011 17:15:28 -0400 Message-ID: <4E711969.8030400@web.de> Date: Wed, 14 Sep 2011 23:15:21 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4E70EC90.8000904@us.ibm.com> <4E7100E9.70305@web.de> <4E7103AE.5060201@codemonkey.ws> In-Reply-To: <4E7103AE.5060201@codemonkey.ws> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig05704FDCABF7FBCE783CE23F" Sender: jan.kiszka@web.de Subject: Re: [Qemu-devel] [RFC] Plan for moving forward with QOM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel , "Edgar E. Iglesias" , Gerd Hoffmann , Markus Armbruster , Peter Maydell This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig05704FDCABF7FBCE783CE23F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-09-14 21:42, Anthony Liguori wrote: >> Such names can get fairly long I'm afraid... >=20 > A user should never even see these names. A user probably will always > interact with devices via paths. Right. But will those automatic names be used at all then? >=20 > We can also look at doing things like user-defined aliases or something= > like that. =2E..or a way to set the name of an auto-generated device via its pathnam= e. >=20 >>> Since a bus is-a device in QOM, there is no notion of having multiple= >>> busses >>> under the same device. A device can implement multiple bus interface= s, >>> but can >>> only be a single bus of any given bus interface. >>> >>> Device names are completely independent of pathnames. For devices th= at >>> are no >>> user created, device names should be treated as opaque blobs with >>> absolutely no >>> semantic meaning. >>> >>> All device relationships are identified as named properties. A QOM p= ath >>> name >>> consists of a named device, >> >> With a system root device called '/'. So '/' is another >> character(-sequence) that is forbidden in device names. >=20 > Yes, but there is no system root device. There is always a generic link to some root device. I think it would be more regular to make that link an abstract device called '/' - maybe even one that can hold a larger number of children. Keeps the door open for crazy multi-root systems models. Jan --------------enig05704FDCABF7FBCE783CE23F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5xGW4ACgkQitSsb3rl5xTpGACggwCqnnwcziTpZ/eE/+dny0L4 ADwAoMgmjowaIF3vvYYnsVsUq2o3Hbnm =e++6 -----END PGP SIGNATURE----- --------------enig05704FDCABF7FBCE783CE23F--