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>,
Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
Yanghang Liu <yanghliu@redhat.com>
Subject: Re: [PATCH 2/6] vfio/migration: Fail adding device with enable-migration=on and existing blocker
Date: Tue, 29 Aug 2023 15:23:36 +0200 [thread overview]
Message-ID: <3e8a7edc-8527-e10c-bf2a-73e01650edd1@redhat.com> (raw)
In-Reply-To: <20230828151842.11303-3-avihaih@nvidia.com>
On 8/28/23 17:18, Avihai Horon wrote:
> If a device with enable-migration=on is added and it causes a migration
> blocker, adding the device should fail with a proper error.
>
> This is not the case with multiple device migration blocker when the
> blocker already exists. If the blocker already exists and a device with
> enable-migration=on is added which causes a migration blocker, adding
> the device will succeed.
>
> Fix it by failing adding the device in such case.
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
>
> Fixes: 8bbcb64a71d8 ("vfio/migration: Make VFIO migration non-experimental")
> Signed-off-by: Avihai Horon <avihaih@nvidia.com>
> ---
> hw/vfio/common.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 8a8d074e18..237101d038 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -394,8 +394,7 @@ int vfio_block_multiple_devices_migration(VFIODevice *vbasedev, Error **errp)
> {
> int ret;
>
> - if (multiple_devices_migration_blocker ||
> - vfio_multiple_devices_migration_is_supported()) {
> + if (vfio_multiple_devices_migration_is_supported()) {
> return 0;
> }
>
> @@ -405,6 +404,10 @@ int vfio_block_multiple_devices_migration(VFIODevice *vbasedev, Error **errp)
> return -EINVAL;
> }
>
> + if (multiple_devices_migration_blocker) {
> + return 0;
> + }
> +
> error_setg(&multiple_devices_migration_blocker,
> "Multiple VFIO devices migration is supported only if all of "
> "them support P2P migration");
next prev parent reply other threads:[~2023-08-29 13:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 15:18 [PATCH 0/6] vfio/migration: Block VFIO migration with postcopy and background snapshot Avihai Horon
2023-08-28 15:18 ` [PATCH 1/6] migration: Add migration prefix to functions in target.c Avihai Horon
2023-08-29 13:23 ` Cédric Le Goater
2023-08-29 14:04 ` Peter Xu
2023-08-29 15:59 ` Avihai Horon
2023-08-28 15:18 ` [PATCH 2/6] vfio/migration: Fail adding device with enable-migration=on and existing blocker Avihai Horon
2023-08-29 13:23 ` Cédric Le Goater [this message]
2023-08-28 15:18 ` [PATCH 3/6] vfio/migration: Add vfio_migratable_devices_num() Avihai Horon
2023-08-29 13:24 ` Cédric Le Goater
2023-08-28 15:18 ` [PATCH 4/6] vfio/migration: Change vfio_mig_active() semantics Avihai Horon
2023-08-28 15:18 ` [PATCH 5/6] vfio/migration: Block VFIO migration with postcopy migration Avihai Horon
2023-08-29 13:24 ` Cédric Le Goater
2023-08-29 15:52 ` Avihai Horon
2023-08-29 14:53 ` Peter Xu
2023-08-29 16:20 ` Avihai Horon
2023-08-29 18:27 ` Peter Xu
2023-08-30 7:01 ` Avihai Horon
2023-08-30 8:37 ` Cédric Le Goater
2023-08-30 9:21 ` Avihai Horon
2023-08-30 9:53 ` Cédric Le Goater
2023-08-30 10:12 ` Avihai Horon
2023-08-30 11:17 ` Cédric Le Goater
2023-08-30 14:22 ` Peter Xu
2023-08-30 16:06 ` Avihai Horon
2023-08-28 15:18 ` [PATCH 6/6] vfio/migration: Block VFIO migration with background snapshot 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=3e8a7edc-8527-e10c-bf2a-73e01650edd1@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yanghliu@redhat.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).