From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47370)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1ZZgdW-0007qA-T1
	for qemu-devel@nongnu.org; Wed, 09 Sep 2015 10:46:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1ZZgdS-0003E9-VV
	for qemu-devel@nongnu.org; Wed, 09 Sep 2015 10:46:10 -0400
Received: from mx2.suse.de ([195.135.220.15]:56877)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1ZZgdS-0003E0-Q7
	for qemu-devel@nongnu.org; Wed, 09 Sep 2015 10:46:06 -0400
References: <87io7j7j4y.fsf@blackfin.pond.sub.org>
From: =?UTF-8?Q?Andreas_F=c3=a4rber?= <afaerber@suse.de>
Message-ID: <55F0462D.8080709@suse.de>
Date: Wed, 9 Sep 2015 16:46:05 +0200
MIME-Version: 1.0
In-Reply-To: <87io7j7j4y.fsf@blackfin.pond.sub.org>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Confused by QOM:
 /machine/unattached/device[5]/dr-connector[255]/fdt
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: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org

Hi Markus,

Am 09.09.2015 um 16:38 schrieb Markus Armbruster:
> I ran into this:
>=20
>     $ qemu-system-ppc64 -nodefaults -S -display none -monitor stdio -ma=
chine pseries-2.4
>     QEMU 2.4.50 monitor - type 'help' for more information
>     (qemu) qom-list /machine/unattached/device[5]/dr-connector[255]
>     fdt (struct)
>     entity-sense (uint32)
>     name (string)
>     connector_type (uint32)
>     index (uint32)
>     id (uint32)
>     allocation-state (uint32)
>     indicator-state (uint32)
>     isolation-state (uint32)
>     parent_bus (link<bus>)
>     hotplugged (bool)
>     hotpluggable (bool)
>     realized (bool)
>     type (string)
>     (qemu) qom-list /machine/unattached/device[5]/dr-connector[255]/fdt
>     Device '/machine/unattached/device[5]/dr-connector[255]/fdt' not fo=
und
>=20
> According to the first qom-list, .../fdt exists.  According to the
> second, it doesn't.

Actually this is fully expected: qom-list operates on QOM objects. The
fdt property returns a struct, which is considered a value QOM-wise, so
to read it you need to use qom-get, not qom-list.

Now, it may well be that visiting a struct does not work as expected, I
remember we ran into issues there, that held up the qom-tree stuff...

Regards,
Andreas

--=20
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Felix Imend=F6rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N=FC=
rnberg)