mirror of https://github.com/xemu-project/xemu.git
migration/ram: Reduce unnecessary rate limiting
When the host page is a huge page and something is sent in the current iteration, migration_rate_limit() should be executed. If not, it can be omitted. Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com> Signed-off-by: Kunkun Jiang <jiangkunkun@huawei.com> Reviewed-by: David Edmondson <david.edmondson@oracle.com> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Message-Id: <20210316125716.1243-2-jiangkunkun@huawei.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
This commit is contained in:
parent
1a37352277
commit
23feba906e
|
@ -2035,8 +2035,13 @@ static int ram_save_host_page(RAMState *rs, PageSearchStatus *pss,
|
|||
|
||||
pages += tmppages;
|
||||
pss->page++;
|
||||
/* Allow rate limiting to happen in the middle of huge pages */
|
||||
migration_rate_limit();
|
||||
/*
|
||||
* Allow rate limiting to happen in the middle of huge pages if
|
||||
* something is sent in the current iteration.
|
||||
*/
|
||||
if (pagesize_bits > 1 && tmppages > 0) {
|
||||
migration_rate_limit();
|
||||
}
|
||||
} while ((pss->page & (pagesize_bits - 1)) &&
|
||||
offset_in_ramblock(pss->block,
|
||||
((ram_addr_t)pss->page) << TARGET_PAGE_BITS));
|
||||
|
|
Loading…
Reference in New Issue