Lines Matching full:migration

810  * Indicates the device can support the migration API through
832  * Upon VFIO_DEVICE_FEATURE_SET, execute a migration state change on the VFIO
836  * The kernel migration driver must fully transition the device to the new state
839  * The kernel migration driver must not generate asynchronous device state
851  * this FD when it is finished. The user must consider the migration data stream
856  * Upon VFIO_DEVICE_FEATURE_GET, get the current migration state of the VFIO
866  * The device migration Finite State Machine is described by the enum
867  * vfio_device_mig_state. Some of the FSM arcs will create a migration data
868  * transfer session by returning a FD, in this case the migration data will
889  *   migration driver must accept and respond to interaction to support external
899  *   kernel migration driver should complete the incorporation of data written
903  *   invalid, the migration driver must fail the SET_STATE ioctl and
927  *   migration state. End of stream on the FD indicates the entire device
931  *   the device is in STOP_COPY or risk corruption of the device migration data
938  *   a compatible device. The migration driver may alter/reset the internal
940  *   migration data.
955  * then it can stop only P2P DMA, otherwise it must stop all DMA. The migration
1052  * migration infrastructure that allows implementing dirty page tracking
1053  * during the pre copy phase of live migration. Only DMA WRITEs are logged,
1117  * restart the dirty tracking, or to abort/restart the whole migration.
1173  * The migration capability allows to report supported features for migration.
1303  * the device; designed to be used when a migration is in progress. Dirty pages