From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: abhijeet inamdar <abhijeetinamdar3005@gmail.com>,
qemu-discuss <qemu-discuss@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: QOM
Date: Tue, 21 Dec 2021 12:59:05 +0100 [thread overview]
Message-ID: <0f468714-96bd-1e5a-0e40-b7fd5f920964@redhat.com> (raw)
In-Reply-To: <CAP4GjT2fC_bTkoNd=21MrdoC1hKk_jejDBdc8KiNvr86aOyAwA@mail.gmail.com>
Hi Abhijeet,
On 12/21/21 12:27, abhijeet inamdar wrote:
> Hi,
>
> 1)What does QOM stand for?
QOM: "QEMU Object Model"
See https://qemu-project.gitlab.io/qemu/devel/qom.html
> 2)Can anyone tell what this error means?
>
> (qemu) Unexpected error in object_property_find() at
> /home/ocp/vcpu-playground/vcpu_on_qemu/qemu-4.2.0/qom/object.c:1177:
> qemu-system-arm: Property '.sysbus-irq[0]' not found
> Aborted (core dumped).
I suppose you are trying to connect a device gpio/irq output line
to another device input, likely using sysbus_connect_irq().
The API is "connect the N-th output line from the SysBus device
to this qemu_irq handler", where qemu_irq is the input line.
Apparently your SysBus device doesn't have any output line
registered. These are registered using sysbus_init_irq().
The first call register the first output IRQ, and so on.
Some objects have their QOM interface documented, for
example to use the ARM GIC see:
https://gitlab.com/qemu-project/qemu/-/blob/master/include/hw/intc/arm_gic.h#L22
Hope that helps.
Regards,
Phil.
next parent reply other threads:[~2021-12-21 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP4GjT2fC_bTkoNd=21MrdoC1hKk_jejDBdc8KiNvr86aOyAwA@mail.gmail.com>
2021-12-21 11:59 ` Philippe Mathieu-Daudé [this message]
2021-12-21 12:18 ` QOM abhijeet inamdar
2021-12-21 12:22 ` QOM abhijeet inamdar
2021-12-21 16:21 ` QOM abhijeet inamdar
2022-01-06 10:27 ` QOM Peter Maydell
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=0f468714-96bd-1e5a-0e40-b7fd5f920964@redhat.com \
--to=philmd@redhat.com \
--cc=abhijeetinamdar3005@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).