On 06/05/2024 7:35, Markus Armbruster wrote:
External email: Use caution opening links or attachments
Avihai Horon <avih...@nvidia.com> writes:
On 02/05/2024 14:19, Markus Armbruster wrote:
External email: Use caution opening links or attachments
Avihai Horon <avih...@nvidia.com> writes:
Add a new QAPI event for VFIO device migration state change. This event
will be emitted when a VFIO device changes its migration 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.
Signed-off-by: Avihai Horon <avih...@nvidia.com>
Can you explain briefly why this event makes sense only for VFIO devices?
VFIO devices have their own protocol for migration and a unique set of
migration states.
This event holds info about these VFIO migration states, which I think cannot
be described in the same accuracy by other events such as run state or
migration states.
Would it make sense to work this into the commit message?
Sure, it wouldn't hurt. I will add it.
