On 16/05/2024 03:04, Fabiano Rosas wrote:
> Li Zhijian via writes:
>
>> Currently, it always returns 0, no need to check the return value at all.
>> In addition, enter colo coroutine only if migration_incoming_colo_enabled()
>> is true.
>> Once the destination side enters the COLO* state, the
Li Zhijian via writes:
> Currently, it always returns 0, no need to check the return value at all.
> In addition, enter colo coroutine only if migration_incoming_colo_enabled()
> is true.
> Once the destination side enters the COLO* state, the COLO process will
> take over the remaining
> -Original Message-
> From: Li Zhijian
> Sent: Thursday, May 9, 2024 11:31 AM
> To: Peter Xu ; Fabiano Rosas
> Cc: Zhang, Hailiang ; qemu-
> de...@nongnu.org; Zhang, Chen ; Li Zhijian
>
> Subject: [PATCH 2/3] migration/colo: make colo_incoming_co() re
On Thu, May 09, 2024 at 11:31:05AM +0800, Li Zhijian via wrote:
> Currently, it always returns 0, no need to check the return value at all.
> In addition, enter colo coroutine only if migration_incoming_colo_enabled()
> is true.
> Once the destination side enters the COLO* state, the COLO process
Currently, it always returns 0, no need to check the return value at all.
In addition, enter colo coroutine only if migration_incoming_colo_enabled()
is true.
Once the destination side enters the COLO* state, the COLO process will
take over the remaining processes until COLO exits.
Signed-off-by:
