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>,
Markus Armbruster <armbru@redhat.com>,
Michael Roth <michael.roth@amd.com>,
Eric Blake <eblake@redhat.com>, Peter Xu <peterx@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Joao Martins <joao.m.martins@oracle.com>,
Maor Gottlieb <maorg@nvidia.com>
Subject: Re: [PATCH v3 2/4] vfio/migration: Emit VFIO migration QAPI event
Date: Wed, 15 May 2024 18:20:46 +0200 [thread overview]
Message-ID: <f8b5017b-a2fa-470a-b97c-41612b737a5d@redhat.com> (raw)
In-Reply-To: <20240515132138.4560-3-avihaih@nvidia.com>
On 5/15/24 15:21, Avihai Horon wrote:
> Emit VFIO migration QAPI event when a VFIO device changes its migration
> state. This can be used by management applications to get updates on the
> current state of the VFIO device for their own purposes.
>
> A new per VFIO device capability, "migration-events", is added so events
> can be enabled only for the required devices. It is disabled by default.
>
> Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
> ---
> include/hw/vfio/vfio-common.h | 1 +
> hw/vfio/migration.c | 59 +++++++++++++++++++++++++++++++++--
> hw/vfio/pci.c | 2 ++
> 3 files changed, 59 insertions(+), 3 deletions(-)
>
> diff --git a/include/hw/vfio/vfio-common.h b/include/hw/vfio/vfio-common.h
> index b9da6c08ef..3ec5f2425e 100644
> --- a/include/hw/vfio/vfio-common.h
> +++ b/include/hw/vfio/vfio-common.h
> @@ -115,6 +115,7 @@ typedef struct VFIODevice {
> bool no_mmap;
> bool ram_block_discard_allowed;
> OnOffAuto enable_migration;
> + bool migration_events;
> VFIODeviceOps *ops;
> unsigned int num_irqs;
> unsigned int num_regions;
> diff --git a/hw/vfio/migration.c b/hw/vfio/migration.c
> index 06ae40969b..2e1a8f6031 100644
> --- a/hw/vfio/migration.c
> +++ b/hw/vfio/migration.c
> @@ -24,6 +24,7 @@
> #include "migration/register.h"
> #include "migration/blocker.h"
> #include "qapi/error.h"
> +#include "qapi/qapi-events-vfio.h"
> #include "exec/ramlist.h"
> #include "exec/ram_addr.h"
> #include "pci.h"
> @@ -80,6 +81,58 @@ static const char *mig_state_to_str(enum vfio_device_mig_state state)
> }
> }
>
> +static VfioMigrationState
> +mig_state_to_qapi_state(enum vfio_device_mig_state state)
> +{
> + switch (state) {
> + case VFIO_DEVICE_STATE_STOP:
> + return QAPI_VFIO_MIGRATION_STATE_STOP;
> + case VFIO_DEVICE_STATE_RUNNING:
> + return QAPI_VFIO_MIGRATION_STATE_RUNNING;
> + case VFIO_DEVICE_STATE_STOP_COPY:
> + return QAPI_VFIO_MIGRATION_STATE_STOP_COPY;
> + case VFIO_DEVICE_STATE_RESUMING:
> + return QAPI_VFIO_MIGRATION_STATE_RESUMING;
> + case VFIO_DEVICE_STATE_RUNNING_P2P:
> + return QAPI_VFIO_MIGRATION_STATE_RUNNING_P2P;
> + case VFIO_DEVICE_STATE_PRE_COPY:
> + return QAPI_VFIO_MIGRATION_STATE_PRE_COPY;
> + case VFIO_DEVICE_STATE_PRE_COPY_P2P:
> + return QAPI_VFIO_MIGRATION_STATE_PRE_COPY_P2P;
> + default:
> + g_assert_not_reached();
> + }
> +}
> +
> +static void vfio_migration_send_event(VFIODevice *vbasedev)
> +{
> + VFIOMigration *migration = vbasedev->migration;
> + DeviceState *dev = vbasedev->dev;
> + g_autofree char *qom_path = NULL;
> + Object *obj;
> +
> + if (!vbasedev->migration_events) {
> + return;
> + }
> +
> + g_assert(vbasedev->ops->vfio_get_object);
> + obj = vbasedev->ops->vfio_get_object(vbasedev);
> + g_assert(obj);
> + qom_path = object_get_canonical_path(obj);
> +
> + qapi_event_send_vfio_migration(
> + dev->id, qom_path, mig_state_to_qapi_state(migration->device_state));
> +}
> +
> +static void vfio_migration_set_device_state(VFIODevice *vbasedev,
> + enum vfio_device_mig_state state)
> +{
> + VFIOMigration *migration = vbasedev->migration;
> +
> + migration->device_state = state;
> + vfio_migration_send_event(vbasedev);
> +}
> +
> static int vfio_migration_set_state(VFIODevice *vbasedev,
> enum vfio_device_mig_state new_state,
> enum vfio_device_mig_state recover_state)
> @@ -125,12 +178,12 @@ static int vfio_migration_set_state(VFIODevice *vbasedev,
> goto reset_device;
> }
>
> - migration->device_state = recover_state;
> + vfio_migration_set_device_state(vbasedev, recover_state);
>
> return ret;
> }
>
> - migration->device_state = new_state;
> + vfio_migration_set_device_state(vbasedev, new_state);
> if (mig_state->data_fd != -1) {
> if (migration->data_fd != -1) {
> /*
> @@ -156,7 +209,7 @@ reset_device:
> strerror(errno));
> }
>
> - migration->device_state = VFIO_DEVICE_STATE_RUNNING;
> + vfio_migration_set_device_state(vbasedev, VFIO_DEVICE_STATE_RUNNING);
>
> return ret;
> }
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 64780d1b79..8840602c50 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -3362,6 +3362,8 @@ static Property vfio_pci_dev_properties[] = {
> VFIO_FEATURE_ENABLE_IGD_OPREGION_BIT, false),
> DEFINE_PROP_ON_OFF_AUTO("enable-migration", VFIOPCIDevice,
> vbasedev.enable_migration, ON_OFF_AUTO_AUTO),
> + DEFINE_PROP_BOOL("migration-events", VFIOPCIDevice,
> + vbasedev.migration_events, false),
> DEFINE_PROP_BOOL("x-no-mmap", VFIOPCIDevice, vbasedev.no_mmap, false),
> DEFINE_PROP_BOOL("x-balloon-allowed", VFIOPCIDevice,
> vbasedev.ram_block_discard_allowed, false),
next prev parent reply other threads:[~2024-05-15 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 13:21 [PATCH v3 0/4] qapi/vfio: Add VFIO migration QAPI event Avihai Horon
2024-05-15 13:21 ` [PATCH v3 1/4] " Avihai Horon
2024-05-15 13:21 ` [PATCH v3 2/4] vfio/migration: Emit " Avihai Horon
2024-05-15 16:20 ` Cédric Le Goater [this message]
2024-05-15 13:21 ` [PATCH v3 3/4] vfio/migration: Don't emit STOP_COPY VFIO migration QAPI event twice Avihai Horon
2024-05-15 13:21 ` [PATCH v3 4/4] vfio/migration: Enhance VFIO migration state tracing Avihai Horon
2024-05-15 16:19 ` Cédric Le Goater
2024-05-16 16:29 ` [PATCH v3 0/4] qapi/vfio: Add VFIO migration QAPI event Cédric Le Goater
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=f8b5017b-a2fa-470a-b97c-41612b737a5d@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=avihaih@nvidia.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=joao.m.martins@oracle.com \
--cc=maorg@nvidia.com \
--cc=michael.roth@amd.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).