qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, anthony.perard@citrix.com,
	peterx@redhat.com, quintela@redhat.com, kwolf@redhat.com,
	imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 4/5] vl: Document dependencies hiding in global and compat props
Date: Tue, 2 Apr 2019 13:14:55 +0100	[thread overview]
Message-ID: <20190402121455.GB2861@work-vm> (raw)
In-Reply-To: <20190401090827.20793-5-armbru@redhat.com>

* Markus Armbruster (armbru@redhat.com) wrote:
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
>  vl.c | 24 ++++++++++++++++++++++--
>  1 file changed, 22 insertions(+), 2 deletions(-)
> 
> diff --git a/vl.c b/vl.c
> index e4d7ad6b85..8c6d06b01d 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -4285,16 +4285,36 @@ int main(int argc, char **argv, char **envp)
>      current_machine->maxram_size = maxram_size;
>      current_machine->ram_slots = ram_slots;
>  
> +    /*
> +     * Note: uses machine properties such as kernel-irqchip, must run
> +     * after machine_set_property().
> +     */
>      configure_accelerator(current_machine, argv[0]);
>  
> +    /*
> +     * Beware, QOM objects created before this point miss global and
> +     * compat properties.
> +     *
> +     * Global properties get set up by qdev_prop_register_global(),
> +     * called from user_register_global_props(), and certain option
> +     * desugaring.

Not to stop this patch series; but could we add a way to actually
detect when this has happened?  Like setting a flag on QOM objects
created before this point for example?

>  Also in CPU feature desugaring (buried in
> +     * parse_cpu_model()), which happens below this point, but may
> +     * only target the CPU type, which can only be created after
> +     * parse_cpu_model() returned the type.
> +     *
> +     * Machine compat properties: object_set_machine_compat_props().
> +     * Accelerator compat props: object_set_accelerator_compat_props(),
> +     * called from configure_accelerator().
> +     */
> +
>      if (!qtest_enabled() && machine_class->deprecation_reason) {
>          error_report("Machine type '%s' is deprecated: %s",
>                       machine_class->name, machine_class->deprecation_reason);
>      }
>  
>      /*
> -     * Migration object can only be created after global properties
> -     * are applied correctly.
> +     * Note: creates a QOM object, must run only after global and
> +     * compat properties have been set up.
>       */
>      migration_object_init();
>  
> -- 
> 2.17.2
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  parent reply	other threads:[~2019-04-02 12:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01  9:08 [Qemu-devel] [PATCH v2 0/5] Compat props bug fixes Markus Armbruster
2019-04-01  9:08 ` [Qemu-devel] [PATCH v2 1/5] Revert "vl: Fix to create migration object before block backends again" Markus Armbruster
2019-04-02 10:50   ` Igor Mammedov
2019-04-02 11:37     ` Markus Armbruster
2019-04-01  9:08 ` [Qemu-devel] [PATCH v2 2/5] Revert "migration: move only_migratable to MigrationState" Markus Armbruster
2019-04-01  9:27   ` Dr. David Alan Gilbert
2019-04-01  9:51     ` Daniel P. Berrangé
2019-04-01 11:31       ` Markus Armbruster
2019-04-01 11:43         ` Daniel P. Berrangé
2019-04-01 13:35           ` Dr. David Alan Gilbert
2019-04-02 10:52   ` Igor Mammedov
2019-04-02 11:49     ` Markus Armbruster
2019-04-02 12:03       ` Dr. David Alan Gilbert
2019-04-01  9:08 ` [Qemu-devel] [PATCH v2 3/5] migration: Support adding migration blockers earlier Markus Armbruster
2019-04-02 10:53   ` Igor Mammedov
2019-04-01  9:08 ` [Qemu-devel] [PATCH v2 4/5] vl: Document dependencies hiding in global and compat props Markus Armbruster
2019-04-02 10:53   ` Igor Mammedov
2019-04-02 12:14   ` Dr. David Alan Gilbert [this message]
2019-04-02 13:11     ` Markus Armbruster
2019-04-01  9:08 ` [Qemu-devel] [PATCH v2 5/5] accel: Unbreak accelerator fallback Markus Armbruster

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=20190402121455.GB2861@work-vm \
    --to=dgilbert@redhat.com \
    --cc=anthony.perard@citrix.com \
    --cc=armbru@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).