Add more detail description for COLO checkpoint use case.
Suggested by Dr. David Alan Gilbert <dgilb...@redhat.com>
Signed-off-by: Zhang Chen <zhangc...@gmail.com>
---
docs/block-replication.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/docs/block-replication.txt b/docs/block-replication.txt
index 6bde6737fb..b6c5e94764 100644
--- a/docs/block-replication.txt
+++ b/docs/block-replication.txt
@@ -131,9 +131,10 @@ a. replication_start_all()
thread.
b. replication_do_checkpoint_all()
This interface is called after all VM state is transferred to
- Secondary QEMU. The Disk buffer will be dropped in this interface.
- The caller must hold the I/O mutex lock if it is in migration/checkpoint
- thread.
+ secondary node, and in primary node this interface no need to
+ called after synchronizing all the states. The Disk buffer will be dropped
+ in this interface. The caller must hold the I/O mutex lock if it is
+ in migration/checkpoint thread.
c. replication_get_error_all()
This interface is called to check if error happened in replication.
The caller must hold the I/O mutex lock if it is in migration/checkpoint
--
2.17.GIT
