From: Fabiano Rosas <farosas@suse.de>
To: Avihai Horon <avihaih@nvidia.com>, qemu-devel@nongnu.org
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Peter Xu" <peterx@redhat.com>, "Wang, Lei" <lei4.wang@intel.com>,
"Joao Martins" <joao.m.martins@oracle.com>,
"Avihai Horon" <avihaih@nvidia.com>
Subject: Re: [PATCH v2 0/3] migration: Don't serialize devices in qemu_savevm_state_iterate()
Date: Mon, 04 Mar 2024 17:36:46 -0300 [thread overview]
Message-ID: <87msrd20pt.fsf@suse.de> (raw)
In-Reply-To: <20240304105339.20713-1-avihaih@nvidia.com>
Avihai Horon <avihaih@nvidia.com> writes:
> Hi,
>
> This small series is v2 of the single patch I previously sent [1].
>
> It removes device serialization in qemu_savevm_state_iterate() and does
> some VFIO migration touch ups. More info provided in the commit
> messages.
>
> Thanks.
>
> Changes from V1 -> V2:
> * Remove device serialization in qemu_savevm_state_iterate() always,
> regardless of switchover-ack.
> * Refactor vfio_save_iterate() return value.
> * Add a note about migration rate limiting in vfio_save_iterate().
>
> [1] https://lore.kernel.org/qemu-devel/20240222155627.14563-1-avihaih@nvidia.com/
>
> Avihai Horon (3):
> migration: Don't serialize devices in qemu_savevm_state_iterate()
> vfio/migration: Refactor vfio_save_state() return value
> vfio/migration: Add a note about migration rate limiting
>
> hw/vfio/migration.c | 12 +++++++-----
> migration/savevm.c | 15 ++++++---------
> 2 files changed, 13 insertions(+), 14 deletions(-)
Series:
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2024-03-04 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 10:53 [PATCH v2 0/3] migration: Don't serialize devices in qemu_savevm_state_iterate() Avihai Horon
2024-03-04 10:53 ` [PATCH v2 1/3] " Avihai Horon
2024-03-04 10:53 ` [PATCH v2 2/3] vfio/migration: Refactor vfio_save_state() return value Avihai Horon
2024-03-04 10:53 ` [PATCH v2 3/3] vfio/migration: Add a note about migration rate limiting Avihai Horon
2024-03-04 20:36 ` Fabiano Rosas [this message]
2024-03-05 2:24 ` [PATCH v2 0/3] migration: Don't serialize devices in qemu_savevm_state_iterate() 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=87msrd20pt.fsf@suse.de \
--to=farosas@suse.de \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=clg@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=lei4.wang@intel.com \
--cc=peterx@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 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).