From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Confused by QOM: /machine/unattached/device[5]/dr-connector[255]/fdt
Date: Wed, 9 Sep 2015 16:46:05 +0200 [thread overview]
Message-ID: <55F0462D.8080709@suse.de> (raw)
In-Reply-To: <87io7j7j4y.fsf@blackfin.pond.sub.org>
Hi Markus,
Am 09.09.2015 um 16:38 schrieb Markus Armbruster:
> I ran into this:
>
> $ qemu-system-ppc64 -nodefaults -S -display none -monitor stdio -machine 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 found
>
> 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
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-09-09 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 14:38 [Qemu-devel] Confused by QOM: /machine/unattached/device[5]/dr-connector[255]/fdt Markus Armbruster
2015-09-09 14:46 ` Andreas Färber [this message]
2015-09-09 15:22 ` Markus Armbruster
2015-09-09 16:04 ` Andreas Färber
2015-09-09 16:16 ` Paolo Bonzini
2015-09-09 16:30 ` Andreas Färber
2015-09-13 2:04 ` Eric Blake
2015-09-10 8:55 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F0462D.8080709@suse.de \
--to=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).