Lines Matching full:migration

413  * migration information. Field accesses from this structure are only supported
447  *        the migration region should be used to resume the device.
478  * 3. Save the state during live migration
496  *    migration region. The sequence to be followed for such transition is given
498  * 3. In live migration of user application, the state transitions from _RUNNING
502  *    the device state data to application through the migration region.
505  *    through the migration region.
508  *    user must not be required to consume all migration data before the device
514  *    received through the migration region to resume the device.
525  *      The user application should read data_offset field from the migration
527  *      offset within the migration region during the _SAVING state or write
533  *      the data copied in the migration region during the _SAVING state and
534  *      write the size in bytes of the data copied in the migration region
537  * The format of the migration region is as follows:
571  *    the migration region.
576  *    migration region.
589  * b. Write migration data starting at the migration region + data_offset for
590  *    the length determined by data_size from the migration source.
592  *    written in the migration region. Vendor driver must return this write
594  *    user-provided migration region data to the device resume state.
599  * example, failing migration or terminating the user application.
1047  * The migration capability allows to report supported features for migration.
1177  * the device; designed to be used when a migration is in progress. Dirty pages