From: "Cédric Le Goater" <clg@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>, qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, joao.m.martins@oracle.com,
avihaih@nvidia.com, chao.p.peng@intel.com
Subject: Re: [PATCH v6 5/7] vfio/migration: Free resources when vfio_migration_realize fails
Date: Mon, 3 Jul 2023 17:44:43 +0200 [thread overview]
Message-ID: <26823c6a-cc90-3a87-c427-f16be1b99c66@redhat.com> (raw)
In-Reply-To: <20230703071510.160712-4-zhenzhong.duan@intel.com>
On 7/3/23 09:15, Zhenzhong Duan wrote:
> When vfio_realize() succeeds, hot unplug will call vfio_exitfn()
> to free resources allocated in vfio_realize(); when vfio_realize()
> fails, vfio_exitfn() is never called and we need to free resources
> in vfio_realize().
>
> In the case that vfio_migration_realize() fails,
> e.g: with -only-migratable & enable-migration=off, we see below:
>
> (qemu) device_add vfio-pci,host=81:11.1,id=vfio1,bus=root1,enable-migration=off
> 0000:81:11.1: Migration disabled
> Error: disallowing migration blocker (--only-migratable) for: 0000:81:11.1: Migration is disabled for VFIO device
>
> If we hotplug again we should see same log as above, but we see:
> (qemu) device_add vfio-pci,host=81:11.1,id=vfio1,bus=root1,enable-migration=off
> Error: vfio 0000:81:11.1: device is already attached
>
> That's because some references to VFIO device isn't released.
> For resources allocated in vfio_migration_realize(), free them by
> jumping to out_deinit path with calling a new function
> vfio_migration_deinit(). For resources allocated in vfio_realize(),
> free them by jumping to de-register path in vfio_realize().
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
The vfio_migration_realize() routine is somewhat difficult to follow
but I don't see how to improve it. May be could move the viommu test
at the beginning ? Anyhow,
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
> ---
> hw/vfio/migration.c | 33 +++++++++++++++++++++++----------
> hw/vfio/pci.c | 1 +
> 2 files changed, 24 insertions(+), 10 deletions(-)
>
> diff --git a/hw/vfio/migration.c b/hw/vfio/migration.c
> index e6e5e85f7580..e3954570c853 100644
> --- a/hw/vfio/migration.c
> +++ b/hw/vfio/migration.c
> @@ -802,6 +802,17 @@ static int vfio_migration_init(VFIODevice *vbasedev)
> return 0;
> }
>
> +static void vfio_migration_deinit(VFIODevice *vbasedev)
> +{
> + VFIOMigration *migration = vbasedev->migration;
> +
> + remove_migration_state_change_notifier(&migration->migration_state);
> + qemu_del_vm_change_state_handler(migration->vm_state);
> + unregister_savevm(VMSTATE_IF(vbasedev->dev), "vfio", vbasedev);
> + vfio_migration_free(vbasedev);
> + vfio_unblock_multiple_devices_migration();
> +}
> +
> static int vfio_block_migration(VFIODevice *vbasedev, Error *err, Error **errp)
> {
> int ret;
> @@ -866,7 +877,7 @@ int vfio_migration_realize(VFIODevice *vbasedev, Error **errp)
> error_setg(&err,
> "%s: VFIO device doesn't support device dirty tracking",
> vbasedev->name);
> - return vfio_block_migration(vbasedev, err, errp);
> + goto add_blocker;
> }
>
> warn_report("%s: VFIO device doesn't support device dirty tracking",
> @@ -875,29 +886,31 @@ int vfio_migration_realize(VFIODevice *vbasedev, Error **errp)
>
> ret = vfio_block_multiple_devices_migration(vbasedev, errp);
> if (ret) {
> - return ret;
> + goto out_deinit;
> }
>
> if (vfio_viommu_preset(vbasedev)) {
> error_setg(&err, "%s: Migration is currently not supported "
> "with vIOMMU enabled", vbasedev->name);
> - return vfio_block_migration(vbasedev, err, errp);
> + goto add_blocker;
> }
>
> trace_vfio_migration_realize(vbasedev->name);
> return 0;
> +
> +add_blocker:
> + ret = vfio_block_migration(vbasedev, err, errp);
> +out_deinit:
> + if (ret) {
> + vfio_migration_deinit(vbasedev);
> + }
> + return ret;
> }
>
> void vfio_migration_exit(VFIODevice *vbasedev)
> {
> if (vbasedev->migration) {
> - VFIOMigration *migration = vbasedev->migration;
> -
> - remove_migration_state_change_notifier(&migration->migration_state);
> - qemu_del_vm_change_state_handler(migration->vm_state);
> - unregister_savevm(VMSTATE_IF(vbasedev->dev), "vfio", vbasedev);
> - vfio_migration_free(vbasedev);
> - vfio_unblock_multiple_devices_migration();
> + vfio_migration_deinit(vbasedev);
> }
>
> if (vbasedev->migration_blocker) {
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index c2cf7454ece6..9154dd929d07 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -3210,6 +3210,7 @@ static void vfio_realize(PCIDevice *pdev, Error **errp)
> ret = vfio_migration_realize(vbasedev, errp);
> if (ret) {
> error_report("%s: Migration disabled", vbasedev->name);
> + goto out_deregister;
> }
> }
>
next prev parent reply other threads:[~2023-07-03 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:15 [PATCH v6 0/7] VFIO migration related refactor and bug fix Zhenzhong Duan
2023-07-03 7:15 ` [PATCH v6 3/7] vfio/pci: Disable INTx in vfio_realize error path Zhenzhong Duan
2023-07-03 7:15 ` [PATCH v6 4/7] vfio/migration: Change vIOMMU blocker from global to per device Zhenzhong Duan
2023-07-03 14:57 ` Cédric Le Goater
2023-07-03 7:15 ` [PATCH v6 5/7] vfio/migration: Free resources when vfio_migration_realize fails Zhenzhong Duan
2023-07-03 15:23 ` Joao Martins
2023-07-03 15:34 ` Avihai Horon
2023-07-03 15:41 ` Cédric Le Goater
2023-07-03 15:44 ` Cédric Le Goater [this message]
2023-07-04 1:56 ` Duan, Zhenzhong
2023-07-04 1:33 ` Duan, Zhenzhong
2023-07-03 7:15 ` [PATCH v6 6/7] vfio/migration: Remove print of "Migration disabled" Zhenzhong Duan
2023-07-03 14:58 ` Cédric Le Goater
2023-07-03 7:15 ` [PATCH v6 7/7] vfio/migration: Return bool type for vfio_migration_realize() Zhenzhong Duan
2023-07-03 14:58 ` Cédric Le Goater
2023-07-03 15:24 ` Joao Martins
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=26823c6a-cc90-3a87-c427-f16be1b99c66@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=chao.p.peng@intel.com \
--cc=joao.m.martins@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@intel.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).