From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org,
"Daniel P. Berrange" <berrange@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: Purpose of QOM properties registered at realize time?
Date: Wed, 7 Oct 2020 16:54:31 +0200 [thread overview]
Message-ID: <117cb090-d9ce-6394-42a2-2ac99fd965b9@redhat.com> (raw)
In-Reply-To: <20201007142742.GV7303@habkost.net>
On 07/10/20 16:27, Eduardo Habkost wrote:
>> It is always wrapped, but (as far as I recall, because I have never
>> worked with GPIOs) they are intentionally QOM properties and not just as
>> an implementation detail. It's meant to be accessible to the user if
>> only through qom-get/qom-set.
>
> Being accessible for debugging would be OK. I'm just worried
> about dynamic QOM properties being part of a stable and supported
> API.
Certainly accessing the properties is only for debugging.
However, I am not sure if the _existence_ of GPIOs as dynamic QOM
properties is part of the API; that is, whether the user has to specify
the names of these properties to create some devices. I don't think
that wouldn't be a problem anyway, what do you think?
Paolo
next prev parent reply other threads:[~2020-10-07 14:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 22:06 Purpose of QOM properties registered at realize time? Eduardo Habkost
2020-10-07 10:35 ` BALATON Zoltan via
2020-10-07 12:04 ` Paolo Bonzini
2020-10-07 13:02 ` Eduardo Habkost
2020-10-07 13:55 ` Paolo Bonzini
2020-10-07 14:27 ` Eduardo Habkost
2020-10-07 14:54 ` Paolo Bonzini [this message]
2020-10-07 15:51 ` Eduardo Habkost
2020-10-07 15:58 ` Peter Maydell
2020-10-07 14:28 ` Peter Maydell
2020-10-07 15:48 ` Eduardo Habkost
2020-10-08 9:45 ` Markus Armbruster
2020-10-08 10:00 ` Peter Maydell
2020-10-08 15:15 ` Eduardo Habkost
2020-10-08 15:41 ` Peter Maydell
2020-10-12 10:30 ` 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=117cb090-d9ce-6394-42a2-2ac99fd965b9@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-riscv@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).