From: Alex Williamson <alex.williamson@redhat.com>
To: Kirti Wankhede <kwankhede@nvidia.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 v29 05/17] vfio: Add VM state change handler to know state of VM
Date: Mon, 26 Oct 2020 08:02:57 -0600 [thread overview]
Message-ID: <20201026080257.2f9d3506@w520.home> (raw)
In-Reply-To: <ce6c6864-a8a3-269e-a9c2-3fe4d2b265b8@nvidia.com>
On Mon, 26 Oct 2020 19:18:51 +0530
Kirti Wankhede <kwankhede@nvidia.com> wrote:
> On 10/26/2020 6:30 PM, Alex Williamson wrote:
> > On Mon, 26 Oct 2020 15:06:15 +0530
> > Kirti Wankhede <kwankhede@nvidia.com> wrote:
> >
> >> VM state change handler is called on change in VM's state. Based on
> >> VM state, VFIO device state should be changed.
> >> Added read/write helper functions for migration region.
> >> Added function to set device_state.
> >>
> >> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
> >> Reviewed-by: Neo Jia <cjia@nvidia.com>
> >> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> >> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
> >> ---
> >> hw/vfio/migration.c | 158 ++++++++++++++++++++++++++++++++++++++++++
> >> hw/vfio/trace-events | 2 +
> >> include/hw/vfio/vfio-common.h | 4 ++
> >> 3 files changed, 164 insertions(+)
> >>
> >> diff --git a/hw/vfio/migration.c b/hw/vfio/migration.c
> >> index fd7faf423cdc..65ce735d667b 100644
> >> --- a/hw/vfio/migration.c
> >> +++ b/hw/vfio/migration.c
> > [snip]
> >> @@ -64,6 +216,9 @@ static int vfio_migration_init(VFIODevice *vbasedev,
> >> ret = -EINVAL;
> >> goto err;
> >> }
> >> +
> >> + migration->vm_state = qemu_add_vm_change_state_handler(vfio_vmstate_change,
> >> + vbasedev);
> >> return 0;
> >>
> >> err:
> >
> > Fails to build, @migration is not defined. We could use
> > vbasedev->migration or pull defining and setting @migration from patch
> > 06. Thanks,
> >
>
> Pulling and setting migration from patch 06 seems better option.
> Should I resend patch 5 & 6 only?
I've resolved this locally as patch 05:
@@ -38,6 +190,7 @@ static int vfio_migration_init(VFIODevice *vbasedev,
{
int ret;
Object *obj;
+ VFIOMigration *migration;
if (!vbasedev->ops->vfio_get_object) {
return -EINVAL;
@@ -64,6 +217,10 @@ static int vfio_migration_init(VFIODevice *vbasedev,
ret = -EINVAL;
goto err;
}
+
+ migration = vbasedev->migration;
+ migration->vm_state = qemu_add_vm_change_state_handler(vfio_vmstate_change,
+ vbasedev);
return 0;
err:
patch 06:
@@ -219,8 +243,11 @@ static int vfio_migration_init(VFIODevice *vbasedev,
}
migration = vbasedev->migration;
+ migration->vbasedev = vbasedev;
migration->vm_state = qemu_add_vm_change_state_handler(vfio_vmstate_change,
vbasedev);
+ migration->migration_state.notify = vfio_migration_state_notifier;
+ add_migration_state_change_notifier(&migration->migration_state);
return 0;
err:
If you're satisfied with that, no need to resend. Thanks,
Alex
next prev parent reply other threads:[~2020-10-26 14:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 9:36 [PATCH v29 00/17] Add migration support for VFIO devices Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 01/17] vfio: Add function to unmap VFIO region Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 02/17] vfio: Add vfio_get_object callback to VFIODeviceOps Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 03/17] vfio: Add save and load functions for VFIO PCI devices Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 04/17] vfio: Add migration region initialization and finalize function Kirti Wankhede
2020-10-26 16:23 ` Cornelia Huck
2020-10-26 9:36 ` [PATCH v29 05/17] vfio: Add VM state change handler to know state of VM Kirti Wankhede
2020-10-26 13:00 ` Alex Williamson
2020-10-26 13:48 ` Kirti Wankhede
2020-10-26 14:02 ` Alex Williamson [this message]
2020-10-26 14:37 ` Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 06/17] vfio: Add migration state change notifier Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 07/17] vfio: Register SaveVMHandlers for VFIO device Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 08/17] vfio: Add save state functions to SaveVMHandlers Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 09/17] vfio: Add load " Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 10/17] memory: Set DIRTY_MEMORY_MIGRATION when IOMMU is enabled Kirti Wankhede
2020-10-26 16:47 ` Alex Williamson
2020-10-26 16:58 ` Paolo Bonzini
2020-10-26 9:36 ` [PATCH v29 11/17] vfio: Get migration capability flags for container Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 12/17] vfio: Add function to start and stop dirty pages tracking Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 13/17] vfio: Add vfio_listener_log_sync to mark dirty pages Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 14/17] vfio: Dirty page tracking when vIOMMU is enabled Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 15/17] vfio: Add ioctl to get dirty pages bitmap during dma unmap Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 16/17] vfio: Make vfio-pci device migration capable Kirti Wankhede
2020-10-26 9:36 ` [PATCH v29 17/17] qapi: Add VFIO devices migration stats in Migration stats Kirti Wankhede
2021-03-15 13:08 ` Thomas Huth
2021-03-16 13:22 ` Eric Blake
2021-03-16 13:24 ` Eric Blake
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=20201026080257.2f9d3506@w520.home \
--to=alex.williamson@redhat.com \
--cc=Ken.Xue@amd.com \
--cc=Zhengxiao.zx@Alibaba-inc.com \
--cc=aik@ozlabs.ru \
--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=kwankhede@nvidia.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 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).