All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirti Wankhede <kwankhede@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: cohuck@redhat.com, cjia@nvidia.com, zhi.wang.linux@gmail.com,
	aik@ozlabs.ru, Zhengxiao.zx@Alibaba-inc.com,
	shuangtai.tst@alibaba-inc.com, qemu-devel@nongnu.org,
	peterx@redhat.com, eauger@redhat.com, artemp@nvidia.com,
	yi.l.liu@intel.com, quintela@redhat.com, ziye.yang@intel.com,
	armbru@redhat.com, mlevitsk@redhat.com, pasic@linux.ibm.com,
	felipe@nutanix.com, zhi.a.wang@intel.com, mcrossley@nvidia.com,
	kevin.tian@intel.com, yan.y.zhao@intel.com, dgilbert@redhat.com,
	changpeng.liu@intel.com, eskultet@redhat.com, Ken.Xue@amd.com,
	jonathan.davies@nutanix.com, pbonzini@redhat.com,
	dnigam@nvidia.com
Subject: Re: [PATCH v28 04/17] vfio: Add migration region initialization and finalize function
Date: Sat, 24 Oct 2020 20:18:52 +0530	[thread overview]
Message-ID: <aa23198f-1581-b8ee-2d65-837391bbae04@nvidia.com> (raw)
In-Reply-To: <20201024082100.216d9c29@x1.home>



On 10/24/2020 7:51 PM, Alex Williamson wrote:
> On Sat, 24 Oct 2020 15:09:14 +0530
> Kirti Wankhede <kwankhede@nvidia.com> wrote:
> 
>> On 10/23/2020 10:22 PM, Alex Williamson wrote:
>>> On Fri, 23 Oct 2020 16:10:30 +0530
>>> Kirti Wankhede <kwankhede@nvidia.com> wrote:
>>>    
>>>> Whether the VFIO device supports migration or not is decided based of
>>>> migration region query. If migration region query is successful and migration
>>>> region initialization is successful then migration is supported else
>>>> migration is blocked.
>>>>
>>>> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
>>>> Reviewed-by: Neo Jia <cjia@nvidia.com>
>>>> Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>>>> ---
>>>>    hw/vfio/meson.build           |   1 +
>>>>    hw/vfio/migration.c           | 133 ++++++++++++++++++++++++++++++++++++++++++
>>>>    hw/vfio/trace-events          |   3 +
>>>>    include/hw/vfio/vfio-common.h |   9 +++
>>>>    4 files changed, 146 insertions(+)
>>>>    create mode 100644 hw/vfio/migration.c
>>>>
>>>> diff --git a/hw/vfio/meson.build b/hw/vfio/meson.build
>>>> index 37efa74018bc..da9af297a0c5 100644
>>>> --- a/hw/vfio/meson.build
>>>> +++ b/hw/vfio/meson.build
>>>> @@ -2,6 +2,7 @@ vfio_ss = ss.source_set()
>>>>    vfio_ss.add(files(
>>>>      'common.c',
>>>>      'spapr.c',
>>>> +  'migration.c',
>>>>    ))
>>>>    vfio_ss.add(when: 'CONFIG_VFIO_PCI', if_true: files(
>>>>      'display.c',
>>>> diff --git a/hw/vfio/migration.c b/hw/vfio/migration.c
>>>> new file mode 100644
>>>> index 000000000000..bbe6e0b7a6cc
>>>> --- /dev/null
>>>> +++ b/hw/vfio/migration.c
>>>> @@ -0,0 +1,133 @@
>>>> +/*
>>>> + * Migration support for VFIO devices
>>>> + *
>>>> + * Copyright NVIDIA, Inc. 2020
>>>> + *
>>>> + * This work is licensed under the terms of the GNU GPL, version 2. See
>>>> + * the COPYING file in the top-level directory.
>>>> + */
>>>> +
>>>> +#include "qemu/osdep.h"
>>>> +#include <linux/vfio.h>
>>>> +
>>>> +#include "hw/vfio/vfio-common.h"
>>>> +#include "cpu.h"
>>>> +#include "migration/migration.h"
>>>> +#include "migration/qemu-file.h"
>>>> +#include "migration/register.h"
>>>> +#include "migration/blocker.h"
>>>> +#include "migration/misc.h"
>>>> +#include "qapi/error.h"
>>>> +#include "exec/ramlist.h"
>>>> +#include "exec/ram_addr.h"
>>>> +#include "pci.h"
>>>> +#include "trace.h"
>>>> +
>>>> +static void vfio_migration_region_exit(VFIODevice *vbasedev)
>>>> +{
>>>> +    VFIOMigration *migration = vbasedev->migration;
>>>> +
>>>> +    if (!migration) {
>>>> +        return;
>>>> +    }
>>>> +
>>>> +    vfio_region_exit(&migration->region);
>>>> +    vfio_region_finalize(&migration->region);
>>>
>>> I think it would make sense to also:
>>>
>>> g_free(migration);
>>> vbasedev->migration = NULL;
>>>
>>> here as well so the callers don't need to.
>>
>> No, vfio_migration_init() case, err case is also hit when
>> vbasedev->migration is not yet set but local variable migration is not-NULL.
> 
> So why do we even call vfio_migration_region_exit() for that error
> case?  It seems that could just g_free(migration); return ret; rather
> than goto err.  Thanks,
> 

Removing temporary local variable, with that above 2 can be moved to 
exit function.

Thanks,
Kirti

> Alex
> 
>>> Not worth a re-spin itself,
>>> maybe a follow-up if there's no other reason for a re-spin.  Thanks,
>>>
>>> Alex
>>>    
>>>> +}
>>>> +
>>>> +static int vfio_migration_init(VFIODevice *vbasedev,
>>>> +                               struct vfio_region_info *info)
>>>> +{
>>>> +    int ret;
>>>> +    Object *obj;
>>>> +    VFIOMigration *migration;
>>>> +
>>>> +    if (!vbasedev->ops->vfio_get_object) {
>>>> +        return -EINVAL;
>>>> +    }
>>>> +
>>>> +    obj = vbasedev->ops->vfio_get_object(vbasedev);
>>>> +    if (!obj) {
>>>> +        return -EINVAL;
>>>> +    }
>>>> +
>>>> +    migration = g_new0(VFIOMigration, 1);
>>>> +
>>>> +    ret = vfio_region_setup(obj, vbasedev, &migration->region,
>>>> +                            info->index, "migration");
>>>> +    if (ret) {
>>>> +        error_report("%s: Failed to setup VFIO migration region %d: %s",
>>>> +                     vbasedev->name, info->index, strerror(-ret));
>>>> +        goto err;
>>>> +    }
>>>> +
>>>> +    vbasedev->migration = migration;
>>>> +
>>>> +    if (!migration->region.size) {
>>>> +        error_report("%s: Invalid zero-sized of VFIO migration region %d",
>>>> +                     vbasedev->name, info->index);
>>>> +        ret = -EINVAL;
>>>> +        goto err;
>>>> +    }
>>>> +    return 0;
>>>> +
>>>> +err:
>>>> +    vfio_migration_region_exit(vbasedev);
>>>> +    g_free(migration);
>>>> +    vbasedev->migration = NULL;
>>>> +    return ret;
>>>> +}
>>>> +
>>>> +/* ---------------------------------------------------------------------- */
>>>> +
>>>> +int vfio_migration_probe(VFIODevice *vbasedev, Error **errp)
>>>> +{
>>>> +    struct vfio_region_info *info = NULL;
>>>> +    Error *local_err = NULL;
>>>> +    int ret;
>>>> +
>>>> +    ret = vfio_get_dev_region_info(vbasedev, VFIO_REGION_TYPE_MIGRATION,
>>>> +                                   VFIO_REGION_SUBTYPE_MIGRATION, &info);
>>>> +    if (ret) {
>>>> +        goto add_blocker;
>>>> +    }
>>>> +
>>>> +    ret = vfio_migration_init(vbasedev, info);
>>>> +    if (ret) {
>>>> +        goto add_blocker;
>>>> +    }
>>>> +
>>>> +    g_free(info);
>>>> +    trace_vfio_migration_probe(vbasedev->name, info->index);
>>>> +    return 0;
>>>> +
>>>> +add_blocker:
>>>> +    error_setg(&vbasedev->migration_blocker,
>>>> +               "VFIO device doesn't support migration");
>>>> +    g_free(info);
>>>> +
>>>> +    ret = migrate_add_blocker(vbasedev->migration_blocker, &local_err);
>>>> +    if (local_err) {
>>>> +        error_propagate(errp, local_err);
>>>> +        error_free(vbasedev->migration_blocker);
>>>> +        vbasedev->migration_blocker = NULL;
>>>> +    }
>>>> +    return ret;
>>>> +}
>>>> +
>>>> +void vfio_migration_finalize(VFIODevice *vbasedev)
>>>> +{
>>>> +    VFIOMigration *migration = vbasedev->migration;
>>>> +
>>>> +    if (migration) {
>>>> +        vfio_migration_region_exit(vbasedev);
>>>> +        g_free(vbasedev->migration);
>>>> +        vbasedev->migration = NULL;
>>>> +    }
>>>> +
>>>> +    if (vbasedev->migration_blocker) {
>>>> +        migrate_del_blocker(vbasedev->migration_blocker);
>>>> +        error_free(vbasedev->migration_blocker);
>>>> +        vbasedev->migration_blocker = NULL;
>>>> +    }
>>>> +}
>>>> diff --git a/hw/vfio/trace-events b/hw/vfio/trace-events
>>>> index a0c7b49a2ebc..9ced5ec6277c 100644
>>>> --- a/hw/vfio/trace-events
>>>> +++ b/hw/vfio/trace-events
>>>> @@ -145,3 +145,6 @@ vfio_display_edid_link_up(void) ""
>>>>    vfio_display_edid_link_down(void) ""
>>>>    vfio_display_edid_update(uint32_t prefx, uint32_t prefy) "%ux%u"
>>>>    vfio_display_edid_write_error(void) ""
>>>> +
>>>> +# migration.c
>>>> +vfio_migration_probe(const char *name, uint32_t index) " (%s) Region %d"
>>>> diff --git a/include/hw/vfio/vfio-common.h b/include/hw/vfio/vfio-common.h
>>>> index ba6169cd926e..8275c4c68f45 100644
>>>> --- a/include/hw/vfio/vfio-common.h
>>>> +++ b/include/hw/vfio/vfio-common.h
>>>> @@ -57,6 +57,10 @@ typedef struct VFIORegion {
>>>>        uint8_t nr; /* cache the region number for debug */
>>>>    } VFIORegion;
>>>>    
>>>> +typedef struct VFIOMigration {
>>>> +    VFIORegion region;
>>>> +} VFIOMigration;
>>>> +
>>>>    typedef struct VFIOAddressSpace {
>>>>        AddressSpace *as;
>>>>        QLIST_HEAD(, VFIOContainer) containers;
>>>> @@ -113,6 +117,8 @@ typedef struct VFIODevice {
>>>>        unsigned int num_irqs;
>>>>        unsigned int num_regions;
>>>>        unsigned int flags;
>>>> +    VFIOMigration *migration;
>>>> +    Error *migration_blocker;
>>>>    } VFIODevice;
>>>>    
>>>>    struct VFIODeviceOps {
>>>> @@ -204,4 +210,7 @@ int vfio_spapr_create_window(VFIOContainer *container,
>>>>    int vfio_spapr_remove_window(VFIOContainer *container,
>>>>                                 hwaddr offset_within_address_space);
>>>>    
>>>> +int vfio_migration_probe(VFIODevice *vbasedev, Error **errp);
>>>> +void vfio_migration_finalize(VFIODevice *vbasedev);
>>>> +
>>>>    #endif /* HW_VFIO_VFIO_COMMON_H */
>>>    
>>
> 


  reply	other threads:[~2020-10-24 14:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 10:40 [PATCH v28 00/17] Add migration support for VFIO devices Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 01/17] vfio: Add function to unmap VFIO region Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 02/17] vfio: Add vfio_get_object callback to VFIODeviceOps Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 03/17] vfio: Add save and load functions for VFIO PCI devices Kirti Wankhede
2020-10-24 11:53   ` Yan Zhao
2020-10-24 14:16     ` Alex Williamson
2020-10-24 19:48       ` Kirti Wankhede
2020-10-24 20:23         ` Alex Williamson
2020-10-25  4:26       ` Yan Zhao
2020-10-23 10:40 ` [PATCH v28 04/17] vfio: Add migration region initialization and finalize function Kirti Wankhede
2020-10-23 11:24   ` Cornelia Huck
2020-10-24 20:22     ` Kirti Wankhede
2020-10-23 16:52   ` Alex Williamson
2020-10-24  9:39     ` Kirti Wankhede
2020-10-24 14:21       ` Alex Williamson
2020-10-24 14:48         ` Kirti Wankhede [this message]
2020-10-23 10:40 ` [PATCH v28 05/17] vfio: Add VM state change handler to know state of VM Kirti Wankhede
2020-10-23 11:32   ` Cornelia Huck
2020-10-24 20:27     ` Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 06/17] vfio: Add migration state change notifier Kirti Wankhede
2020-10-23 11:45   ` Cornelia Huck
2020-10-23 10:40 ` [PATCH v28 07/17] vfio: Register SaveVMHandlers for VFIO device Kirti Wankhede
2020-10-23 12:18   ` Cornelia Huck
2020-10-24 11:26   ` Yan Zhao
2020-10-24 20:35     ` Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 08/17] vfio: Add save state functions to SaveVMHandlers Kirti Wankhede
2020-10-24 11:59   ` Yan Zhao
2020-10-23 10:40 ` [PATCH v28 09/17] vfio: Add load " Kirti Wankhede
2020-10-24 11:58   ` Yan Zhao
2020-10-23 10:40 ` [PATCH v28 10/17] memory: Set DIRTY_MEMORY_MIGRATION when IOMMU is enabled Kirti Wankhede
2020-10-24 12:00   ` Yan Zhao
2020-10-23 10:40 ` [PATCH v28 11/17] vfio: Get migration capability flags for container Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 12/17] vfio: Add function to start and stop dirty pages tracking Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 13/17] vfio: Add vfio_listener_log_sync to mark dirty pages Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 14/17] vfio: Dirty page tracking when vIOMMU is enabled Kirti Wankhede
2020-10-24 11:56   ` Yan Zhao
2020-10-23 10:40 ` [PATCH v28 15/17] vfio: Add ioctl to get dirty pages bitmap during dma unmap Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 16/17] vfio: Make vfio-pci device migration capable Kirti Wankhede
2020-10-23 10:40 ` [PATCH v28 17/17] qapi: Add VFIO devices migration stats in Migration stats Kirti Wankhede
2020-10-24 16:56 ` [PATCH v28 00/17] Add migration support for VFIO devices Philippe Mathieu-Daudé
2020-10-24 17:48   ` Kirti Wankhede
2020-10-24 19:43     ` Philippe Mathieu-Daudé

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=aa23198f-1581-b8ee-2d65-837391bbae04@nvidia.com \
    --to=kwankhede@nvidia.com \
    --cc=Ken.Xue@amd.com \
    --cc=Zhengxiao.zx@Alibaba-inc.com \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=armbru@redhat.com \
    --cc=artemp@nvidia.com \
    --cc=changpeng.liu@intel.com \
    --cc=cjia@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=dnigam@nvidia.com \
    --cc=eauger@redhat.com \
    --cc=eskultet@redhat.com \
    --cc=felipe@nutanix.com \
    --cc=jonathan.davies@nutanix.com \
    --cc=kevin.tian@intel.com \
    --cc=mcrossley@nvidia.com \
    --cc=mlevitsk@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=shuangtai.tst@alibaba-inc.com \
    --cc=yan.y.zhao@intel.com \
    --cc=yi.l.liu@intel.com \
    --cc=zhi.a.wang@intel.com \
    --cc=zhi.wang.linux@gmail.com \
    --cc=ziye.yang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.