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>, "Peter Xu" <peterx@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: Wed, 04 Feb 2026 15:29:20 +0100 [thread overview]
Message-ID: <87bji4vayn.fsf@pond.sub.org> (raw)
In-Reply-To: <af10c110-d2ec-4b92-b33e-7f259c3d7646@nvidia.com> (Avihai Horon's message of "Wed, 4 Feb 2026 15:39:21 +0200")
Avihai Horon <avihaih@nvidia.com> writes:
> On 2/4/2026 3:24 PM, Markus Armbruster wrote:
[...]
>> Except for the subject line: "vfio/migration: Send VFIO_MIGRATION event
>> before PRE_COPY_P2P transition" become misleading in v2.
>
> Can you explain why misleading?
>
> Prior to this patch VFIO_MIGRATION event was sent only after PRE_COPY_P2P transition.
> Now with this patch VFIO_MIGRATION event is sent also before PRE_COPY_P2P transition.
Nevermind, I got confused :)
prev parent reply other threads:[~2026-02-04 14:29 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
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 [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=87bji4vayn.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=farosas@suse.de \
--cc=maorg@nvidia.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 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.