From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33540) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SEn0a-0002gn-OR for qemu-devel@nongnu.org; Mon, 02 Apr 2012 15:33:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SEn0Y-00043l-VO for qemu-devel@nongnu.org; Mon, 02 Apr 2012 15:33:44 -0400 Received: from fmmailgate07.web.de ([217.72.192.248]:51260) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SEn0Y-00043F-PC for qemu-devel@nongnu.org; Mon, 02 Apr 2012 15:33:42 -0400 Received: from moweb002.kundenserver.de (moweb002.kundenserver.de [172.19.20.108]) by fmmailgate07.web.de (Postfix) with ESMTP id 76AF2FF2BE6 for ; Mon, 2 Apr 2012 21:33:40 +0200 (CEST) Message-ID: <4F79FF0E.9090701@web.de> Date: Mon, 02 Apr 2012 21:33:34 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig230A7957DFCD6412E6750A73" Subject: [Qemu-devel] qdev property listing broken List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig230A7957DFCD6412E6750A73 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Anthony, I noticed that only properties with legacy names are printed via info qtree. After digging through the qdev and qom property maze, it turned out the property registration in qdev_property_add_legacy and qdev_property_add_static is not consistent with the access in qdev_print_props. The latter assumes all properties are strings, the former generate the full set of types - and add_legacy obviously an inconsistent one, dependent on the existence of print/parse handlers. I fail to see the right direction, ie. where to fix this. Can you provide a hint? Jan PS: It's really no fun to understand and debug this code anymore. Hopefully, the removal of the qdev layer can improve this again. --------------enig230A7957DFCD6412E6750A73 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/ iEYEARECAAYFAk95/xIACgkQitSsb3rl5xTNtACbBGBls1IKqEGeGmEZ9ACqre2Q vncAoJefsaxNBZhKvmQGcfhylmYSZsk5 =7x8X -----END PGP SIGNATURE----- --------------enig230A7957DFCD6412E6750A73--