From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Claudio Fontana <cfontana@suse.de>, Paolo Bonzini <pbonzini@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: all class init functions for all types in QEMU are called in select_machine(). Expected?
Date: Fri, 12 Mar 2021 10:45:32 +0100 [thread overview]
Message-ID: <a81c0a8d-af3c-4b40-bcb4-9b120b5eee93@redhat.com> (raw)
In-Reply-To: <bdc8dbaf-8d63-833a-3e57-7e823a321486@suse.de>
On 3/12/21 10:31 AM, Claudio Fontana wrote:
> Hello Paolo and all,
>
> while debugging a class init ordering issue, I noticed that
>
> _all_ class init functions for all types registered in the QEMU QOM are called in select_machine().
> Expected?
>
> In particular it happens here:
>
> static MachineClass *select_machine(void)
> {
> GSList *machines = object_class_get_list(TYPE_MACHINE, false);
>
>
> object_class_get_list() ->
> object_class_foreach() ->
> g_hash_table_foreach() ->
> object_class_foreach_tramp ->
> type_initialize(type);
>
>
> Is this really desired? It looks suspect to me.
>
> (gdb) bt
> #0 0x0000555555db613f in arm_v7m_class_init (oc=0x555556dca320, data=0x555556a926e0 <arm_tcg_cpus+288>)
> at ../target/arm/tcg/tcg-cpu-models.c:849
> #1 0x0000555555f1deba in type_initialize (ti=0x555556d5b2f0) at ../qom/object.c:364
> #2 0x0000555555f1f62a in object_class_foreach_tramp (key=0x555556d5b470, value=0x555556d5b2f0, opaque=0x7fffffffda20)
> at ../qom/object.c:1069
> #3 0x00007ffff6562000 in g_hash_table_foreach () at /usr/lib64/libglib-2.0.so.0
> #4 0x0000555555f1f709 in object_class_foreach (fn=
> 0x555555f1f866 <object_class_get_list_tramp>, implements_type=0x555556381b09 "machine", include_abstract=false, opaque=0x7fffffffda70)
> at ../qom/object.c:1091
> #5 0x0000555555f1f8e4 in object_class_get_list (implements_type=0x555556381b09 "machine", include_abstract=false) at ../qom/object.c:1148
> #6 0x0000555555debe94 in select_machine () at ../softmmu/vl.c:1607
>
>
> If not here, where should be the right place, for example, for CPU class inits to be called?
>
> At the very least I would put a comment there around the beginning of select_machine() saying:
>
> /* all types, all classes in QOM are initialized here, as a result of the object_class_get_list call */
>
> Wdyt?
Are you trying to register types conditionally?
next prev parent reply other threads:[~2021-03-12 9:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 9:31 all class init functions for all types in QEMU are called in select_machine(). Expected? Claudio Fontana
2021-03-12 9:45 ` Philippe Mathieu-Daudé [this message]
2021-03-12 9:58 ` Claudio Fontana
2021-03-12 10:07 ` Paolo Bonzini
2021-03-12 10:25 ` Claudio Fontana
2021-03-12 10:39 ` Paolo Bonzini
2021-03-12 11:51 ` Claudio Fontana
2021-03-12 12:02 ` Paolo Bonzini
2021-03-12 13:40 ` Claudio Fontana
2021-03-12 14:00 ` Claudio Fontana
2021-03-12 17:04 ` Paolo Bonzini
2021-03-12 17:24 ` Claudio Fontana
2021-03-12 17:30 ` Paolo Bonzini
2021-03-12 9:46 ` Paolo Bonzini
2021-03-12 9:49 ` Claudio Fontana
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=a81c0a8d-af3c-4b40-bcb4-9b120b5eee93@redhat.com \
--to=philmd@redhat.com \
--cc=cfontana@suse.de \
--cc=ehabkost@redhat.com \
--cc=pbonzini@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).