From: "Michal Prívozník" <mprivozn@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Odd square bracket encoding in QOM names
Date: Tue, 30 Nov 2021 10:41:48 +0100 [thread overview]
Message-ID: <fec32eb4-3b7b-e2b7-29f9-b1795dfeb2eb@redhat.com> (raw)
In-Reply-To: <32fd9815-11b1-686f-5c2b-9d31c72a64c6@ilande.co.uk>
On 11/30/21 09:35, Mark Cave-Ayland wrote:
> Hi all,
>
> Has there been a recent change as to how square brackets are encoded
> within QOM names? I noticed that the output has changed here in the
> "info qom-tree" output in qemu-system-m68k for the q800 machine.
>
> The q800 machine has a set of 256 memory region aliases that used to
> appear in the "info qom-tree" output as:
>
> /mac_m68k.io[100] (memory-region)
> /mac_m68k.io[101] (memory-region)
> /mac_m68k.io[102] (memory-region)
>
> but they now appear as:
>
> /mac_m68k.io\x5b100\x5d[0] (memory-region)
> /mac_m68k.io\x5b101\x5d[0] (memory-region)
> /mac_m68k.io\x5b102\x5d[0] (memory-region)
>
> Is there something that could cause the names to be double-encoded
> before being displayed?
I see the same behavior on x86_64 and qemu-system-x86_64 but with a
different member:
/machine (pc-i440fx-4.0-machine)
/device-memory[0] (memory-region)
/fw_cfg (fw_cfg_io)
/\x2from@etc\x2facpi\x2frsdp[0] (memory-region)
/\x2from@etc\x2facpi\x2ftables[0] (memory-region)
/\x2from@etc\x2ftable-loader[0] (memory-region)
And the same happens over QMP too:
virsh qemu-monitor-command $dom qom-list '"path":"/machine/fw_cfg"'
{"return":[{"name":"type","type":"string"},{"name":"parent_bus","type":"link<bus>"},{"name":"realized","type":"bool"},{"name":"hotplugged","type":"bool"},{"name":"hotpluggable","type":"bool"},{"name":"acpi-mr-restore","type":"bool"},{"name":"x-file-slots","type":"uint16"},{"name":"dma_enabled","type":"bool"},{"name":"\\x2from@etc\\x2facpi\\x2ftables[0]","type":"child<memory-region>"},{"name":"fwcfg.dma[0]","type":"child<memory-region>"},{"name":"fwcfg[0]","type":"child<memory-region>"},{"name":"\\x2from@etc\\x2facpi\\x2frsdp[0]","type":"child<memory-region>"},{"name":"\\x2from@etc\\x2ftable-loader[0]","type":"child<memory-region>"}],"id":"libvirt-455"}
Michal
next prev parent reply other threads:[~2021-11-30 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 8:35 Odd square bracket encoding in QOM names Mark Cave-Ayland
2021-11-30 9:41 ` Michal Prívozník [this message]
2021-12-01 13:58 ` Philippe Mathieu-Daudé
2021-11-30 16:41 ` Peter Maydell
2021-11-30 18:44 ` Mark Cave-Ayland
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=fec32eb4-3b7b-e2b7-29f9-b1795dfeb2eb@redhat.com \
--to=mprivozn@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).