From: Alex Williamson <alex.williamson@redhat.com>
To: Avihai Horon <avihaih@nvidia.com>
Cc: qemu-devel@nongnu.org, "Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Eric Farman" <farman@linux.ibm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"David Hildenbrand" <david@redhat.com>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Thomas Huth" <thuth@redhat.com>,
"Juan Quintela" <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Fam Zheng" <fam@euphon.net>, "Eric Blake" <eblake@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
"John Snow" <jsnow@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
qemu-s390x@nongnu.org, qemu-block@nongnu.org,
"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>,
"Joao Martins" <joao.m.martins@oracle.com>
Subject: Re: [PATCH v9 10/14] vfio/migration: Implement VFIO migration protocol v2
Date: Tue, 7 Feb 2023 16:42:09 -0700 [thread overview]
Message-ID: <20230207164209.03951381.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230206123137.31149-11-avihaih@nvidia.com>
On Mon, 6 Feb 2023 14:31:33 +0200
Avihai Horon <avihaih@nvidia.com> wrote:
> @@ -523,6 +745,41 @@ static int vfio_save_iterate(QEMUFile *f, void *opaque)
> return 0;
> }
>
> +static int vfio_save_complete_precopy(QEMUFile *f, void *opaque)
> +{
> + VFIODevice *vbasedev = opaque;
> + enum vfio_device_mig_state recover_state;
> + int ret;
> +
> + /* We reach here with device state STOP only */
> + recover_state = VFIO_DEVICE_STATE_STOP;
Why do we need to put this in a local variable?
> + ret = vfio_migration_set_state(vbasedev, VFIO_DEVICE_STATE_STOP_COPY,
> + recover_state);
> + if (ret) {
> + return ret;
> + }
> +
> + do {
> + ret = vfio_save_block(f, vbasedev->migration);
> + if (ret < 0) {
> + return ret;
> + }
> + } while (!ret);
> +
> + qemu_put_be64(f, VFIO_MIG_FLAG_END_OF_STATE);
> + ret = qemu_file_get_error(f);
> + if (ret) {
> + return ret;
> + }
> +
> + recover_state = VFIO_DEVICE_STATE_ERROR;
IIRC, the ERROR state is not reachable as a user directed state. I
suppose passing it as the recovery state guarantees a device reset when
it fails, but if that's the intention it should be documented with a
comment to explain so (and vfio_migration_set_state() should not bother
trying to use it as a recovery state).
> + ret = vfio_migration_set_state(vbasedev, VFIO_DEVICE_STATE_STOP,
> + recover_state);
> + trace_vfio_save_complete_precopy(vbasedev->name, ret);
> +
> + return ret;
> +}
> +
> static int vfio_v1_save_complete_precopy(QEMUFile *f, void *opaque)
> {
> VFIODevice *vbasedev = opaque;
...
> @@ -769,12 +1087,17 @@ static void vfio_migration_state_notifier(Notifier *notifier, void *data)
> case MIGRATION_STATUS_CANCELLED:
> case MIGRATION_STATUS_FAILED:
> bytes_transferred = 0;
> - ret = vfio_migration_v1_set_state(vbasedev,
> - ~(VFIO_DEVICE_STATE_V1_SAVING |
> - VFIO_DEVICE_STATE_V1_RESUMING),
> - VFIO_DEVICE_STATE_V1_RUNNING);
> - if (ret) {
> - error_report("%s: Failed to set state RUNNING", vbasedev->name);
> + if (migration->v2) {
> + vfio_migration_set_state(vbasedev, VFIO_DEVICE_STATE_RUNNING,
> + VFIO_DEVICE_STATE_ERROR);
Same here. Thanks,
Alex
> + } else {
> + ret = vfio_migration_v1_set_state(vbasedev,
> + ~(VFIO_DEVICE_STATE_V1_SAVING |
> + VFIO_DEVICE_STATE_V1_RESUMING),
> + VFIO_DEVICE_STATE_V1_RUNNING);
> + if (ret) {
> + error_report("%s: Failed to set state RUNNING", vbasedev->name);
> + }
> }
> }
> }
next prev parent reply other threads:[~2023-02-07 23:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 12:31 [PATCH v9 00/14] vfio/migration: Implement VFIO migration protocol v2 Avihai Horon
2023-02-06 12:31 ` [PATCH v9 01/14] linux-headers: Update to v6.2-rc1 Avihai Horon
2023-02-06 12:31 ` [PATCH v9 02/14] migration: No save_live_pending() method uses the QEMUFile parameter Avihai Horon
2023-02-06 12:31 ` [PATCH v9 03/14] vfio/migration: Fix NULL pointer dereference bug Avihai Horon
2023-02-06 12:31 ` [PATCH v9 04/14] vfio/migration: Allow migration without VFIO IOMMU dirty tracking support Avihai Horon
2023-02-06 12:31 ` [PATCH v9 05/14] migration/qemu-file: Add qemu_file_get_to_fd() Avihai Horon
2023-02-06 12:31 ` [PATCH v9 06/14] vfio/common: Change vfio_devices_all_running_and_saving() logic to equivalent one Avihai Horon
2023-02-06 12:31 ` [PATCH v9 07/14] vfio/migration: Block multiple devices migration Avihai Horon
2023-02-07 22:34 ` Alex Williamson
2023-02-08 13:08 ` Avihai Horon
2023-02-08 16:44 ` Cédric Le Goater
2023-02-08 17:16 ` Avihai Horon
2023-02-08 17:22 ` Alex Williamson
2023-02-08 17:35 ` Avihai Horon
2023-02-06 12:31 ` [PATCH v9 08/14] vfio/migration: Move migration v1 logic to vfio_migration_init() Avihai Horon
2023-02-06 12:31 ` [PATCH v9 09/14] vfio/migration: Rename functions/structs related to v1 protocol Avihai Horon
2023-02-06 12:31 ` [PATCH v9 10/14] vfio/migration: Implement VFIO migration protocol v2 Avihai Horon
2023-02-07 23:42 ` Alex Williamson [this message]
2023-02-08 13:15 ` Avihai Horon
2023-02-06 12:31 ` [PATCH v9 11/14] vfio/migration: Optimize vfio_save_pending() Avihai Horon
2023-02-06 12:31 ` [PATCH v9 12/14] vfio/migration: Remove VFIO migration protocol v1 Avihai Horon
2023-02-06 12:31 ` [PATCH v9 13/14] vfio: Alphabetize migration section of VFIO trace-events file Avihai Horon
2023-02-06 12:31 ` [PATCH v9 14/14] docs/devel: Align VFIO migration docs to v2 protocol Avihai Horon
2023-02-07 23:49 ` Alex Williamson
2023-02-08 13:18 ` Avihai Horon
2023-02-08 17:25 ` Cédric Le Goater
2023-02-08 17:40 ` Avihai Horon
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=20230207164209.03951381.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=jsnow@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=targupta@nvidia.com \
--cc=thuth@redhat.com \
--cc=vsementsov@yandex-team.ru \
--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).