Re: [Xen-devel] [PATCH 3 of 4] libxc: provide notification of final checkpoint to restore end

[Brendan Cully <brendan@xxxxxxxxx>]

On Friday, 03 September 2010 at 14:06, Ian Campbell wrote:
> # HG changeset patch
> # User Ian Campbell <ian.campbell@xxxxxxxxxx>
> # Date 1283519033 -3600
> # Node ID 684cfeffdb1b4bacd736bc05ae26211cb91833df
> # Parent  de66ba50997cd8670fceffa7b01b50704f82edc7
> libxc: provide notification of final checkpoint to restore end
> 
> When the restore code sees this notification it will restore the
> currently in-progress checkpoint when it completes.
> 
> This allows the restore end to finish up without waiting for a
> spurious timeout on the receive fd and thereby avoids unnecessary
> error logging in the case of a successful migration or restore.
> 
> In the normal migration or restore case the first checkpoint is always
> the last. For a rolling checkpoint (such as Remus) the notification is
> currently unused but could be used in the future for example to
> provide a controlled failover for reasons other than error
> 
> Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

This looks sane and passes basic testing here.

Acked-by: Brendan Cully <brendan@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel