From: Peter Xu <peterx@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: Avihai Horon <avihaih@nvidia.com>,
qemu-devel@nongnu.org, Alex Williamson <alex@shazbot.org>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Fabiano Rosas <farosas@suse.de>, Maor Gottlieb <maorg@nvidia.com>
Subject: Re: [PATCH v3] vfio/migration: Send VFIO_MIGRATION event before PRE_COPY_P2P transition
Date: Tue, 3 Feb 2026 12:02:04 -0500 [thread overview]
Message-ID: <aYIqDAdld4a41VDy@x1.local> (raw)
In-Reply-To: <24ea8ccb-d904-49e4-bd27-5378aac4a56a@redhat.com>
On Tue, Feb 03, 2026 at 05:48:11PM +0100, Cédric Le Goater wrote:
> Peter, Fabiano,
>
> Do you think it would be interesting to send VFIO migration events
> by default ?
No objection here.
IIUC it's a matter of why it got introduced with default off in the middle
of 2024? If it's about compatibility of any old mgmt which may be
surprised by these events, then we want to know if they're ready, and then
if we need a compat field for it in older machine types (or enable it even
with old machines).
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2026-02-03 17:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 17:34 [PATCH v3] vfio/migration: Send VFIO_MIGRATION event before PRE_COPY_P2P transition Avihai Horon
2026-02-03 16:27 ` Cédric Le Goater
2026-02-03 16:48 ` Cédric Le Goater
2026-02-03 17:02 ` Peter Xu [this message]
2026-02-03 17:25 ` Avihai Horon
2026-02-11 13:01 ` Avihai Horon
2026-02-11 13:16 ` Cédric Le Goater
2026-02-11 17:45 ` Avihai Horon
2026-02-16 12:22 ` Cédric Le Goater
2026-02-16 13:25 ` Avihai Horon
2026-02-16 17:40 ` Cédric Le Goater
2026-02-17 13:05 ` Avihai Horon
2026-02-17 14:04 ` Cédric Le Goater
2026-02-17 14:39 ` Avihai Horon
2026-02-04 13:22 ` Markus Armbruster
2026-02-04 13:24 ` Markus Armbruster
2026-02-04 13:39 ` Avihai Horon
2026-02-04 14:29 ` Markus Armbruster
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=aYIqDAdld4a41VDy@x1.local \
--to=peterx@redhat.com \
--cc=alex@shazbot.org \
--cc=armbru@redhat.com \
--cc=avihaih@nvidia.com \
--cc=clg@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=maorg@nvidia.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.