RE: [PATCH v4 07/10] migration: split migration_incoming_co

2023-05-04 Thread Zhang, Chen
> -Original Message- > From: Vladimir Sementsov-Ogievskiy > Sent: Thursday, May 4, 2023 6:52 AM > To: Peter Xu > Cc: qemu-devel@nongnu.org; lukasstra...@web.de; quint...@redhat.com; > Zhang, Chen ; Zhang, Hailiang > ; Leonardo Bras > Subject: Re: [PATCH v4

Re: [PATCH v4 07/10] migration: split migration_incoming_co

2023-05-03 Thread Vladimir Sementsov-Ogievskiy
On 02.05.23 23:48, Peter Xu wrote: On Fri, Apr 28, 2023 at 10:49:25PM +0300, Vladimir Sementsov-Ogievskiy wrote: Originally, migration_incoming_co was introduced by 25d0c16f625feb3b6 "migration: Switch to COLO process after finishing loadvm" to be able to enter from COLO code to one

Re: [PATCH v4 07/10] migration: split migration_incoming_co

2023-05-02 Thread Peter Xu
On Fri, Apr 28, 2023 at 10:49:25PM +0300, Vladimir Sementsov-Ogievskiy wrote: > Originally, migration_incoming_co was introduced by > 25d0c16f625feb3b6 >"migration: Switch to COLO process after finishing loadvm" > to be able to enter from COLO code to one specific yield point, added > by

[PATCH v4 07/10] migration: split migration_incoming_co

2023-04-28 Thread Vladimir Sementsov-Ogievskiy
Originally, migration_incoming_co was introduced by 25d0c16f625feb3b6 "migration: Switch to COLO process after finishing loadvm" to be able to enter from COLO code to one specific yield point, added by 25d0c16f625feb3b6. Later in 923709896b1b0 "migration: poll the cm event for destination