From: "Cédric Le Goater" <clg@redhat.com>
To: Avihai Horon <avihaih@nvidia.com>, qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Joao Martins <joao.m.martins@oracle.com>,
Yishai Hadas <yishaih@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Tarun Gupta <targupta@nvidia.com>,
Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH for-8.2 v3 1/6] vfio/migration: Move from STOP_COPY to STOP in vfio_save_cleanup()
Date: Mon, 7 Aug 2023 17:53:25 +0200 [thread overview]
Message-ID: <cc6d0b1c-036f-00f8-41fb-6ef1c59cafa2@redhat.com> (raw)
In-Reply-To: <20230802081449.2528-2-avihaih@nvidia.com>
[ Adding Juan and Peter for their awareness ]
On 8/2/23 10:14, Avihai Horon wrote:
> Changing the device state from STOP_COPY to STOP can take time as the
> device may need to free resources and do other operations as part of the
> transition. Currently, this is done in vfio_save_complete_precopy() and
> therefore it is counted in the migration downtime.
>
> To avoid this, change the device state from STOP_COPY to STOP in
> vfio_save_cleanup(), which is called after migration has completed and
> thus is not part of migration downtime.
What bothers me is that this looks like a device specific optimization
and we are loosing the error part.
I wonder if we could use the PRECOPY_NOTIFY_CLEANUP notifier instead and
modify qemu_savevm_state_cleanup() to return the error which could then
be handled by the caller.
No need to resend the whole series. I think 2-6 are good for merge, I will
probably push them on vfio-next when -rc3 is out.
Thanks,
C.
> Signed-off-by: Avihai Horon <avihaih@nvidia.com>
> ---
> hw/vfio/migration.c | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/hw/vfio/migration.c b/hw/vfio/migration.c
> index 2674f4bc47..8acd182a8b 100644
> --- a/hw/vfio/migration.c
> +++ b/hw/vfio/migration.c
> @@ -383,6 +383,19 @@ static void vfio_save_cleanup(void *opaque)
> VFIODevice *vbasedev = opaque;
> VFIOMigration *migration = vbasedev->migration;
>
> + /*
> + * Changing device state from STOP_COPY to STOP can take time. Do it here,
> + * after migration has completed, so it won't increase downtime.
> + */
> + if (migration->device_state == VFIO_DEVICE_STATE_STOP_COPY) {
> + /*
> + * If setting the device in STOP state fails, the device should be
> + * reset. To do so, use ERROR state as a recover state.
> + */
> + vfio_migration_set_state(vbasedev, VFIO_DEVICE_STATE_STOP,
> + VFIO_DEVICE_STATE_ERROR);
> + }
> +
> g_free(migration->data_buffer);
> migration->data_buffer = NULL;
> migration->precopy_init_size = 0;
> @@ -508,12 +521,6 @@ static int vfio_save_complete_precopy(QEMUFile *f, void *opaque)
> return ret;
> }
>
> - /*
> - * If setting the device in STOP state fails, the device should be reset.
> - * To do so, use ERROR state as a recover state.
> - */
> - ret = vfio_migration_set_state(vbasedev, VFIO_DEVICE_STATE_STOP,
> - VFIO_DEVICE_STATE_ERROR);
> trace_vfio_save_complete_precopy(vbasedev->name, ret);
>
> return ret;
next prev parent reply other threads:[~2023-08-07 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 8:14 [PATCH for-8.2 v3 0/6] vfio/migration: Add P2P support for VFIO migration Avihai Horon
2023-08-02 8:14 ` [PATCH for-8.2 v3 1/6] vfio/migration: Move from STOP_COPY to STOP in vfio_save_cleanup() Avihai Horon
2023-08-07 15:53 ` Cédric Le Goater [this message]
2023-08-08 6:23 ` Avihai Horon
2023-08-08 12:46 ` Jason Gunthorpe
2023-08-11 10:29 ` Cédric Le Goater
2023-08-13 5:35 ` Avihai Horon
2023-08-02 8:14 ` [PATCH for-8.2 v3 2/6] sysemu: Add prepare callback to struct VMChangeStateEntry Avihai Horon
2023-08-02 8:14 ` [PATCH for-8.2 v3 3/6] qdev: Add qdev_add_vm_change_state_handler_full() Avihai Horon
2023-08-02 8:14 ` [PATCH for-8.2 v3 4/6] vfio/migration: Refactor PRE_COPY and RUNNING state checks Avihai Horon
2023-08-02 8:14 ` [PATCH for-8.2 v3 5/6] vfio/migration: Add P2P support for VFIO migration Avihai Horon
2023-08-02 8:43 ` Cédric Le Goater
2023-08-28 7:35 ` YangHang Liu
2023-08-02 8:14 ` [PATCH for-8.2 v3 6/6] vfio/migration: Allow migration of multiple P2P supporting devices Avihai Horon
2023-08-28 7:50 ` [PATCH for-8.2 v3 0/6] vfio/migration: Add P2P support for VFIO migration YangHang Liu
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=cc6d0b1c-036f-00f8-41fb-6ef1c59cafa2@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=kwankhede@nvidia.com \
--cc=maorg@nvidia.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=targupta@nvidia.com \
--cc=yishaih@nvidia.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).