qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	devel@lists.libvirt.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>
Subject: Re: [PATCH v2 3/6] migration: Remove 'blk/-b' option from migrate commands
Date: Mon, 29 Apr 2024 14:18:57 -0300	[thread overview]
Message-ID: <875xw0f5oe.fsf@suse.de> (raw)
In-Reply-To: <Zi_CNIYAi6UbxJ0j@x1n>

Peter Xu <peterx@redhat.com> writes:

> On Fri, Apr 26, 2024 at 10:14:05AM -0300, Fabiano Rosas wrote:
>> @@ -2003,21 +1997,7 @@ static bool migrate_prepare(MigrationState *s, bool blk, bool resume,
>>          }
>>      }
>>  
>> -    if (blk) {
>> -        if (migrate_colo()) {
>> -            error_setg(errp, "No disk migration is required in COLO mode");
>> -            return false;
>> -        }
>> -        if (migrate_block()) {
>> -            error_setg(errp, "Command options are incompatible with "
>> -                       "current migration capabilities");
>> -            return false;
>> -        }
>> -        if (!migrate_cap_set(MIGRATION_CAPABILITY_BLOCK, true, errp)) {
>> -            return false;
>> -        }
>> -        s->must_remove_block_options = true;
>> -    }
>> +    s->must_remove_block_options = true;
>
> Can we drop this var too?  Perhaps with block_cleanup_parameters()?

Yes, Markus mentioned it in v1 already. Take a look there. There's
several other declarations I missed. v3 is coming soon.


  reply	other threads:[~2024-04-29 17:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26 13:14 [PATCH v2 0/6] migration removals & deprecations Fabiano Rosas
2024-04-26 13:14 ` [PATCH v2 1/6] migration: Remove 'skipped' field from MigrationStats Fabiano Rosas
2024-04-29 19:50   ` Peter Xu
2024-04-26 13:14 ` [PATCH v2 2/6] migration: Remove 'inc' option from migrate command Fabiano Rosas
2024-04-29 19:51   ` Peter Xu
2024-04-26 13:14 ` [PATCH v2 3/6] migration: Remove 'blk/-b' option from migrate commands Fabiano Rosas
2024-04-29 15:52   ` Peter Xu
2024-04-29 17:18     ` Fabiano Rosas [this message]
2024-04-29 18:27       ` Peter Xu
2024-04-29 18:35         ` Fabiano Rosas
2024-04-29 18:53           ` Peter Xu
2024-04-26 13:14 ` [PATCH v2 4/6] migration: Remove block migration Fabiano Rosas
2024-04-26 13:14 ` [PATCH v2 5/6] migration: Remove non-multifd compression Fabiano Rosas
2024-04-29 19:52   ` Peter Xu
2024-04-26 13:14 ` [PATCH v2 6/6] migration: Deprecate fd: for file migration Fabiano Rosas
2024-04-29 18:40   ` Peter Xu
2024-04-29 18:47     ` Fabiano Rosas
2024-04-29 19:07       ` Peter Xu

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=875xw0f5oe.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=bleal@redhat.com \
    --cc=devel@lists.libvirt.org \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@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).