From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-riscv@nongnu.org, qemu-arm@nongnu.org, qemu-ppc@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: Purpose of QOM properties registered at realize time?
Date: Mon, 12 Oct 2020 11:30:11 +0100 [thread overview]
Message-ID: <a5b35b51-5fb0-eb7d-7c9e-c876d2e1fcce@ilande.co.uk> (raw)
In-Reply-To: <20201006220647.GR7303@habkost.net>
On 06/10/2020 23:06, Eduardo Habkost wrote:
> Hi,
>
> While trying to understand how QOM properties are used in QEMU, I
> stumbled upon multiple cases where alias properties are added at
> realize time.
>
> Now, I don't understand why those properties exist. As the
> properties are added at realize time, I assume they aren't
> supposed to be touched by the user at all. If they are not
> supposed to be touched by the user, what exactly is the purpose
> of those QOM properties?
>
> For reference, these are the cases I've found:
(cut)
> --
> hw/misc/mac_via.c=1011=static void mac_via_realize(DeviceState *dev, Error **errp)
> hw/misc/mac_via.c:1028: object_property_add_alias(OBJECT(dev), "irq[0]", OBJECT(ms),
This one was me trying to work out how to wire up an IRQ from a child device embedded
within the macio device - I'll send a patch to remove it shortly.
ATB,
Mark.
prev parent reply other threads:[~2020-10-12 10:32 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
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 [this message]
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=a5b35b51-5fb0-eb7d-7c9e-c876d2e1fcce@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@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).