uapi/linux/vfio.h

990  * Indicates the device can support the migration API through
1020  * Upon VFIO_DEVICE_FEATURE_SET, execute a migration state change on the VFIO
1024  * The kernel migration driver must fully transition the device to the new state
1027  * The kernel migration driver must not generate asynchronous device state
1039  * this FD when it is finished. The user must consider the migration data stream
1044  * Upon VFIO_DEVICE_FEATURE_GET, get the current migration state of the VFIO
1054  * The device migration Finite State Machine is described by the enum
1055  * vfio_device_mig_state. Some of the FSM arcs will create a migration data
1056  * transfer session by returning a FD, in this case the migration data will
1082  *   migration driver must accept and respond to interaction to support external
1092  *   kernel migration driver should complete the incorporation of data written
1096  *   invalid, the migration driver must fail the SET_STATE ioctl and
1129  *   new data_fd. The migration driver may perform actions such as enabling
1148  *   migration state. End of stream on the FD indicates the entire device
1152  *   the device is in STOP_COPY or risk corruption of the device migration data
1159  *   a compatible device. The migration driver may alter/reset the internal
1161  *   migration data.
1183  * then it can stop only P2P DMA, otherwise it must stop all DMA. The migration
1228  * This ioctl is used on the migration data FD in the precopy phase of the
1229  * migration data transfer. It returns an estimate of the current data sizes
1234  * return -EINVAL from any other migration state.
1243  * value and decrease as migration data is read from the device.
1261  * During pre-copy the migration data FD has a temporary "end of stream" that is
1268  * Once in STOP_COPY the migration data FD has a permanent end of stream
1348  * migration infrastructure that allows implementing dirty page tracking
1349  * during the pre copy phase of live migration. Only DMA WRITEs are logged,
1413  * restart the dirty tracking, or to abort/restart the whole migration.
1504  * The migration capability allows to report supported features for migration.
1633  * the device; designed to be used when a migration is in progress. Dirty pages