Lines Matching full:migration
403 * migration information. Field accesses from this structure are only supported
437 * the migration region should be used to resume the device.
468 * 3. Save the state during live migration
486 * migration region. The sequence to be followed for such transition is given
488 * 3. In live migration of user application, the state transitions from _RUNNING
492 * the device state data to application through the migration region.
495 * through the migration region.
498 * user must not be required to consume all migration data before the device
504 * received through the migration region to resume the device.
515 * The user application should read data_offset field from the migration
517 * offset within the migration region during the _SAVING state or write
523 * the data copied in the migration region during the _SAVING state and
524 * write the size in bytes of the data copied in the migration region
527 * The format of the migration region is as follows:
561 * the migration region.
566 * migration region.
579 * b. Write migration data starting at the migration region + data_offset for
580 * the length determined by data_size from the migration source.
582 * written in the migration region. Vendor driver must return this write
584 * user-provided migration region data to the device resume state.
589 * example, failing migration or terminating the user application.
1032 * The migration capability allows to report supported features for migration.
1141 * the device; designed to be used when a migration is in progress. Dirty pages