All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Avihai Horon <avihaih@nvidia.com>
Cc: qemu-devel@nongnu.org, "Alex Williamson" <alex@shazbot.org>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Eric Blake" <eblake@redhat.com>
Subject: Re: [PATCH] vfio/migration: Send migration event before device state transition
Date: Wed, 04 Feb 2026 14:03:19 +0100	[thread overview]
Message-ID: <87343gy82w.fsf@pond.sub.org> (raw)
In-Reply-To: <20260128105159.10282-1-avihaih@nvidia.com> (Avihai Horon's message of "Wed, 28 Jan 2026 12:51:59 +0200")

Avihai Horon <avihaih@nvidia.com> writes:

> Currently, VFIO device migration event is sent after the device state
> transition has been completed. However, it may be useful to additionally
> send a "prepare" event before the state transition, to notify users that
> it's about to happen.
>
> For example, in some cases with heavy resource utilization, stopping the
> VFIO device may take a long time. In time-sensitive scenarios, the
> management application that consumes the event may be notified about the
> state transition too late.
>
> To overcome this issue, send an additional "prepare" migration event
> before the device state transition.
>
> Signed-off-by: Avihai Horon <avihaih@nvidia.com>
> ---
>  qapi/vfio.json      | 33 +++++++++++++++++++++++++++++++++
>  hw/vfio/migration.c | 18 +++++++++++++-----
>  2 files changed, 46 insertions(+), 5 deletions(-)
>
> diff --git a/qapi/vfio.json b/qapi/vfio.json
> index a1a9c5b673..de41211f1d 100644
> --- a/qapi/vfio.json
> +++ b/qapi/vfio.json
> @@ -66,3 +66,36 @@
>        'qom-path': 'str',
>        'device-state': 'QapiVfioMigrationState'
>    } }
> +
> +##
> +# @VFIO_MIGRATION_PREPARE:
> +#
> +# This event is emitted when a VFIO device migration state is about to
> +# be changed.  Note that even if this event is received for state X,
> +# the VFIO device may transition to a different state if the original
> +# state transition to X failed.
> +#
> +# @device-id: The device's id, if it has one.
> +#
> +# @qom-path: The device's QOM path.
> +#
> +# @device-state: The new device migration state that is about to be
> +#     changed.
> +#
> +# Since: 11.0
> +#
> +# .. qmp-example::
> +#
> +#     <- { "timestamp": { "seconds": 1713771323, "microseconds": 212268 },
> +#          "event": "VFIO_MIGRATION_PREPARE",
> +#          "data": {
> +#              "device-id": "vfio_dev1",
> +#              "qom-path": "/machine/peripheral/vfio_dev1",
> +#              "device-state": "stop" } }
> +##
> +{ 'event': 'VFIO_MIGRATION_PREPARE',
> +  'data': {
> +      'device-id': 'str',
> +      'qom-path': 'str',
> +      'device-state': 'QapiVfioMigrationState'
> +  } }

The QAPI schema is fine, so

Acked-by: Markus Armbruster <armbru@redhat.com>

Whether the event makes sense I have no idea.  I'm leaving that
judgement to the migration and VFIO maintainers.



  parent reply	other threads:[~2026-02-04 13:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 10:51 [PATCH] vfio/migration: Send migration event before device state transition Avihai Horon
2026-01-28 11:03 ` Cédric Le Goater
2026-01-28 14:49   ` Peter Xu
2026-01-28 15:32     ` Avihai Horon
2026-01-28 16:21       ` Peter Xu
2026-01-28 17:13         ` Avihai Horon
2026-01-28 17:38           ` Peter Xu
2026-01-29  5:11             ` Avihai Horon
2026-01-29 14:31               ` Cédric Le Goater
2026-01-29 21:18                 ` Avihai Horon
2026-01-30 13:34                   ` Cédric Le Goater
2026-02-04 13:03 ` Markus Armbruster [this message]
2026-02-04 13:12   ` Avihai Horon

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=87343gy82w.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alex@shazbot.org \
    --cc=avihaih@nvidia.com \
    --cc=clg@redhat.com \
    --cc=eblake@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 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.