All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: kwolf@redhat.com, quintela@redhat.com, dgilbert@redhat.com,
	peterx@redhat.com, qemu-devel@nongnu.org,
	anthony.perard@citrix.com
Subject: Re: [Qemu-devel] [PATCH v2 1/5] Revert "vl: Fix to create migration object before block backends again"
Date: Tue, 02 Apr 2019 13:37:45 +0200	[thread overview]
Message-ID: <87r2akd4dy.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190402125034.1a052992@redhat.com> (Igor Mammedov's message of "Tue, 2 Apr 2019 12:50:34 +0200")

Igor Mammedov <imammedo@redhat.com> writes:

> On Mon,  1 Apr 2019 11:08:23 +0200
> Markus Armbruster <armbru@redhat.com> wrote:
>
>> This reverts commit e60483f2f8498ae08ae79ca4c6fb03a3317f5e1e.
>> 
>> Recent commit cda4aa9a5a0 moved block backend creation before machine
>> property evaluation.
>
> Side note:
> I've also looked at
>  "[PATCH v3 11/12] pc: Support firmware configuration  with -blockdev"
> that caused movement and have a similar issue with hostmem backends
> where I wanted to set machine.inital-ram-memdev property pointing to
> backend. But hostmem backends are created, since they have to be created
> after machine_set_properties/configure_accelerator due to dependencies.
>
> After some playing around with link property on machine and trying
> to untangle dependency chain I gave up (doesn't look feasible).
> Idea with aliasing like with blockdev won't work either due to
> dependencies (also it looks to me to be quite complicated one).
> So I've resorted to "usual" machine practice 'machine.set_string_property'
> and deal with 'id' referred by it later at machine_run_board_init() time to
> instantiate initial RAM, when we already created all backends.

That's... horrible.  How many of these monstrosities have crept in?

Let's discuss once the RC circus has moved to the next town.

>> This broke block backends registering migration
>> blockers.  Commit e60483f2f84 fixed it by moving migration object
>> creation before block backend creation.  This broke migration with
>> Xen.  Turns out we need to configure the accelerator before we create
>> the migration object so that Xen's accelerator compat properties get
>> applied.  Revert the flawed commit.  This fixes the Xen regression,
>> but brings back the block backend regression.  The next commits will
>> fix it again.
>> 
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>

Thanks!

  reply	other threads:[~2019-04-02 11:37 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 [this message]
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
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=87r2akd4dy.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=anthony.perard@citrix.com \
    --cc=dgilbert@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.