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 v4 2/4] migration: refactor ram_save_target_page functions
Date: Mon, 27 Jan 2025 15:46:40 -0300	[thread overview]
Message-ID: <87v7u0qelr.fsf@suse.de> (raw)
In-Reply-To: <20250127120823.144949-3-ppandit@redhat.com>

Prasad Pandit <ppandit@redhat.com> writes:

> From: Prasad Pandit <pjp@fedoraproject.org>
>
> Refactor ram_save_target_page legacy and multifd
> functions into one. Other than simplifying it,
> it frees 'migration_ops' object from usage, so it
> is expunged.
>
> Signed-off-by: Prasad Pandit <pjp@fedoraproject.org>

Reviewed-by: Fabiano Rosas <farosas@suse.de>


  reply	other threads:[~2025-01-27 18:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27 12:08 [PATCH v4 0/4] Allow to enable multifd and postcopy migration together Prasad Pandit
2025-01-27 12:08 ` [PATCH v4 1/4] migration/multifd: move macros to multifd header Prasad Pandit
2025-01-27 12:08 ` [PATCH v4 2/4] migration: refactor ram_save_target_page functions Prasad Pandit
2025-01-27 18:46   ` Fabiano Rosas [this message]
2025-01-27 12:08 ` [PATCH v4 3/4] migration: enable multifd and postcopy together Prasad Pandit
2025-01-27 12:08 ` [PATCH v4 4/4] tests/qtest/migration: add postcopy tests with multifd Prasad Pandit
2025-01-27 21:13   ` Fabiano Rosas
2025-01-28  5:30     ` Prasad Pandit
2025-01-28 11:17       ` Prasad Pandit
2025-01-28 13:50         ` Fabiano Rosas
2025-01-28 16:45           ` 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=87v7u0qelr.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.