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 0/4] qapi/vfio: Add VFIO migration QAPI event
Date: Thu, 16 May 2024 18:29:29 +0200 [thread overview]
Message-ID: <bff59c81-35e8-40c4-86a6-1f571073d61d@redhat.com> (raw)
In-Reply-To: <20240515132138.4560-1-avihaih@nvidia.com>
On 5/15/24 15:21, Avihai Horon wrote:
> Hello,
>
> This series adds a new QAPI event for VFIO device migration state
> change. This event will be emitted when a VFIO device changes its
> state, for example, during migration or when stopping/starting the
> guest.
>
> This event 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.
>
> Feedback/comments are appreciated,
Applied to vfio-next.
Thanks,
C.
>
> Thanks.
>
> Changes from v2 [2]:
> * Added assert for vbasedev->ops->vfio_get_object and obj. (Cedric)
> * Renamed set_state() to vfio_migration_set_device_state(). (Cedric)
> * Enhanced tracing of device state change. (Cedric)
> * Added Cedric's R-b.
>
> Changes from v1 [1]:
> * Added more info to patch #1 commit mesasge. (Markus)
> * Renamed VFIODeviceMigState to VfioMigrationState and
> VFIO_DEVICE_MIG_STATE_CHANGED to VFIO_MIGRATION. (Joao, Markus)
> * Added qom-path and qdev id to VFIO_MIGRATION event data. (Markus)
> * Handled no-op state transitions in vfio_migration_set_state().
> (Cedric)
> * Added helper to set VFIO state and emit VFIO event. (Peter)
>
> [1]
> https://lore.kernel.org/qemu-devel/20240430051621.19597-1-avihaih@nvidia.com/
>
> [2]
> https://lore.kernel.org/qemu-devel/20240509090954.16447-1-avihaih@nvidia.com/
>
> Avihai Horon (4):
> qapi/vfio: Add VFIO migration QAPI event
> vfio/migration: Emit VFIO migration QAPI event
> vfio/migration: Don't emit STOP_COPY VFIO migration QAPI event twice
> vfio/migration: Enhance VFIO migration state tracing
>
> MAINTAINERS | 1 +
> qapi/qapi-schema.json | 1 +
> qapi/vfio.json | 67 +++++++++++++++++++++++++++++++++
> include/hw/vfio/vfio-common.h | 1 +
> hw/vfio/migration.c | 71 ++++++++++++++++++++++++++++++++---
> hw/vfio/pci.c | 2 +
> hw/vfio/trace-events | 3 +-
> qapi/meson.build | 1 +
> 8 files changed, 141 insertions(+), 6 deletions(-)
> create mode 100644 qapi/vfio.json
>
prev parent reply other threads:[~2024-05-16 16:30 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
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 ` Cédric Le Goater [this message]
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=bff59c81-35e8-40c4-86a6-1f571073d61d@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).