On Wed, Jul 24, 2019 at 01:10:24PM +0100, Dr. David Alan Gilbert wrote:
>* Wei Yang (richardw.y...@linux.intel.com) wrote:
>> On Tue, Jul 23, 2019 at 05:47:03PM +0100, Dr. David Alan Gilbert wrote:
>> >* Wei Yang (richardw.y...@linux.intel.com) wrote:
>> >> After cleanup, it would be clear to audie
* Wei Yang (richardw.y...@linux.intel.com) wrote:
> On Tue, Jul 23, 2019 at 05:47:03PM +0100, Dr. David Alan Gilbert wrote:
> >* Wei Yang (richardw.y...@linux.intel.com) wrote:
> >> After cleanup, it would be clear to audience there are two cases
> >> ram_load:
> >>
> >> * precopy
> >> * postc
On Tue, Jul 23, 2019 at 05:47:03PM +0100, Dr. David Alan Gilbert wrote:
>* Wei Yang (richardw.y...@linux.intel.com) wrote:
>> After cleanup, it would be clear to audience there are two cases
>> ram_load:
>>
>> * precopy
>> * postcopy
>>
>> And it is not necessary to check postcopy_running on
* Wei Yang (richardw.y...@linux.intel.com) wrote:
> After cleanup, it would be clear to audience there are two cases
> ram_load:
>
> * precopy
> * postcopy
>
> And it is not necessary to check postcopy_running on each iteration for
> precopy.
>
> Signed-off-by: Wei Yang
> ---
> migration/r
After cleanup, it would be clear to audience there are two cases
ram_load:
* precopy
* postcopy
And it is not necessary to check postcopy_running on each iteration for
precopy.
Signed-off-by: Wei Yang
---
migration/ram.c | 73 +++--
1 file change