All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Prasad Pandit <ppandit@redhat.com>, qemu-devel@nongnu.org
Cc: peterx@redhat.com, berrange@redhat.com,
	Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH v1 2/4] migration: remove multifd check with postcopy
Date: Tue, 26 Nov 2024 18:12:50 -0300	[thread overview]
Message-ID: <87h67tn1gt.fsf@suse.de> (raw)
In-Reply-To: <20241126115748.118683-3-ppandit@redhat.com>

Prasad Pandit <ppandit@redhat.com> writes:

> From: Prasad Pandit <pjp@fedoraproject.org>
>
> Remove multifd capability check with Postcopy mode.
> This helps to enable both multifd and postcopy together.
>
> Signed-off-by: Prasad Pandit <pjp@fedoraproject.org>
> ---
>  migration/options.c | 5 -----
>  1 file changed, 5 deletions(-)
>
> diff --git a/migration/options.c b/migration/options.c
> index ad8d6989a8..c498558a85 100644
> --- a/migration/options.c
> +++ b/migration/options.c
> @@ -479,11 +479,6 @@ bool migrate_caps_check(bool *old_caps, bool *new_caps, Error **errp)
>              error_setg(errp, "Postcopy is not compatible with ignore-shared");
>              return false;
>          }
> -
> -        if (new_caps[MIGRATION_CAPABILITY_MULTIFD]) {
> -            error_setg(errp, "Postcopy is not yet compatible with multifd");
> -            return false;
> -        }

This should be squashed into patch 4. We don't want to enable what
doesn't work yet.

>      }
>  
>      if (new_caps[MIGRATION_CAPABILITY_BACKGROUND_SNAPSHOT]) {


  reply	other threads:[~2024-11-26 21:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 11:57 [PATCH v1 0/4] Allow to enable multifd and postcopy migration together Prasad Pandit
2024-11-26 11:57 ` [PATCH v1 1/4] migration/multifd: move macros to multifd header Prasad Pandit
2024-11-26 11:57 ` [PATCH v1 2/4] migration: remove multifd check with postcopy Prasad Pandit
2024-11-26 21:12   ` Fabiano Rosas [this message]
2024-11-27 11:43     ` Prasad Pandit
2024-11-26 11:57 ` [PATCH v1 3/4] migration: refactor ram_save_target_page functions Prasad Pandit
2024-11-26 21:18   ` Fabiano Rosas
2024-11-27 11:42     ` Prasad Pandit
2024-11-27 12:19       ` Fabiano Rosas
2024-11-28 10:43         ` Prasad Pandit
2024-11-27 14:12       ` Fabiano Rosas
2024-11-28 10:18         ` Prasad Pandit
2024-11-28 13:19           ` Fabiano Rosas
2024-12-02  9:44             ` Prasad Pandit
2024-12-02 14:12               ` Fabiano Rosas
2024-12-03  5:40                 ` Prasad Pandit
2024-12-05 22:26         ` Peter Xu
2024-11-26 11:57 ` [PATCH v1 4/4] migration: enable multifd and postcopy together Prasad Pandit

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=87h67tn1gt.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=berrange@redhat.com \
    --cc=peterx@redhat.com \
    --cc=pjp@fedoraproject.org \
    --cc=ppandit@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 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.