migration/postcopy: not necessary to discard all RAM at the beginning
PATCH 1/1 migration/postcopy: not necessary to discard all RAM at the beginning
ram_discard_range() unmap page for specific range. To be specific, this clears related page table entries so that userfault would be triggered. But this step is not necessary at the very beginning.
ram_postcopy_incoming_init() is called when destination gets ADVISE command. ADVISE command is sent when migration thread just starts, which implies destination is not running yet. This means no page fault happened and memory region's page tables entries are empty.
This patch removes the discard at the beginning.
--- migration/postcopy-ram.c | 46 ---------------------------------------- migration/postcopy-ram.h | 7 ------ migration/ram.c | 16 -------------- migration/ram.h | 1 - migration/savevm.c | 4 ---- 5 files changed, 74 deletions(-)
migration/postcopy-ram.c +0 -46
@@ -443,32 +443,6 @@ out:return ret; } -/* -* Setup an area of RAM so that it *can* be used for postcopy later; this -* must be done right at the start prior to pre-copy. -* opaque should be the MIS. -*/ -static int init_range (RAMBlock *rb,void *opaque) -{ -const char *block_name =qemu_ram_get_idstr (rb); -void *host_addr =qemu_ram_get_host_addr (rb); -ram_addr_t offset =qemu_ram_get_offset (rb); -ram_addr_t length =qemu_ram_get_used_length (rb); -trace_postcopy_init_range (block_name, host_addr, offset, length); - -/* -* We need the whole of RAM to be truly empty for postcopy, so things -* like ROMs and any data tables built during init must be zero'd -* - we're going to get the copy from the source anyway. -* (Precopy will just overwrite this data, so doesn't need the discard) -*/ -if (ram_discard_range (block_name,0 , length)) { -return -1 ; - } - -return 0 ; -} -/* * At the end of migration, undo the effects of init_range * opaque should be the MIS.
@@ -506,20 +480,6 @@ static int cleanup_range(RAMBlock *rb, void *opaque)return 0 ; } -/* -* Initialise postcopy-ram, setting the RAM to a state where we can go into -* postcopy later; must be called prior to any precopy. -* called from arch_init's similarly named ram_postcopy_incoming_init -*/ -int postcopy_ram_incoming_init (MigrationIncomingState *mis) -{ -if (foreach_not_ignored_block (init_range,NULL )) { -return -1 ; - } - -return 0 ; -} -/* * Manage a single vote to the QEMU balloon inhibitor for all postcopy usage, * last caller wins.
@@ -1282,12 +1242,6 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis)return false; } -int postcopy_ram_incoming_init (MigrationIncomingState *mis) -{ -error_report ("postcopy_ram_incoming_init: No OS support" ); -return -1 ; -} -int postcopy_ram_incoming_cleanup (MigrationIncomingState *mis) {assert (0 );
migration/postcopy-ram.h +0 -7
@@ -22,13 +22,6 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis);*/ int postcopy_ram_incoming_setup (MigrationIncomingState *mis); -/* -* Initialise postcopy-ram, setting the RAM to a state where we can go into -* postcopy later; must be called prior to any precopy. -* called from ram.c's similarly named ram_postcopy_incoming_init -*/ -int postcopy_ram_incoming_init (MigrationIncomingState *mis); -/* * At the end of a migration where postcopy_ram_incoming_init was called. */
migration/ram.c +0 -16
@@ -4015,22 +4015,6 @@ static int ram_load_cleanup(void *opaque)return 0 ; } -/** -* ram_postcopy_incoming_init: allocate postcopy data structures -* -* Returns 0 for success and negative if there was one error -* -* @mis: current migration incoming state -* -* Allocate data structures etc needed by incoming migration with -* postcopy-ram. postcopy-ram's similarly names -* postcopy_ram_incoming_init does the work. -*/ -int ram_postcopy_incoming_init (MigrationIncomingState *mis) -{ -return postcopy_ram_incoming_init (mis); -} -/** * ram_load_postcopy: load a page in postcopy case *
migration/ram.h +0 -1
@@ -58,7 +58,6 @@ void ram_postcopy_migrated_memory_release(MigrationState *ms);int ram_postcopy_send_discard_bitmap (MigrationState *ms);/* For incoming postcopy discard */ int ram_discard_range (const char *block_name,uint64_t start,size_t length); -int ram_postcopy_incoming_init (MigrationIncomingState *mis);bool postcopy_is_running (void );void ram_handle_compressed (void *host,uint8_t ch,uint64_t size);
migration/savevm.c +0 -4
@@ -1674,10 +1674,6 @@ static int loadvm_postcopy_handle_advise(MigrationIncomingState *mis,return -1 ; } -if (ram_postcopy_incoming_init (mis)) { -return -1 ; - } -return 0 ; }
Signature · 1 line
2.17.1
Oops, this one seems to be missed.
Quoted 165 lines · Wei Yang
ram_discard_range()unmap page for specific range. To be specific, this clears related page table entries so that userfault would be triggered. But this step is not necessary at the very beginning.
ram_postcopy_incoming_init()is called when destination gets ADVISE command. ADVISE command is sent when migration thread just starts, which implies destination is not running yet. This means no page fault happened and memory region's page tables entries are empty.This patch removes the discard at the beginning.
Signed-off-by Wei Yang <[email protected]>---
migration/postcopy-ram.c | 46 ---------------------------------------- migration/postcopy-ram.h | 7 ------ migration/ram.c | 16 -------------- migration/ram.h | 1 - migration/savevm.c | 4 ---- 5 files changed, 74 deletions(-)migration/postcopy-ram.c +0
-46@@ -443,32 +443,6 @@ out:return ret; } -/* -* Setup an area of RAM so that it *can* be used for postcopy later; this -* must be done right at the start prior to pre-copy. -* opaque should be the MIS. -*/ -static int init_range (RAMBlock *rb,void *opaque) -{ -const char *block_name =qemu_ram_get_idstr (rb); -void *host_addr =qemu_ram_get_host_addr (rb); -ram_addr_t offset =qemu_ram_get_offset (rb); -ram_addr_t length =qemu_ram_get_used_length (rb); -trace_postcopy_init_range (block_name, host_addr, offset, length); - -/* -* We need the whole of RAM to be truly empty for postcopy, so things -* like ROMs and any data tables built during init must be zero'd -* - we're going to get the copy from the source anyway. -* (Precopy will just overwrite this data, so doesn't need the discard) -*/ -if (ram_discard_range (block_name,0 , length)) { -return -1 ; - } - -return 0 ; -} -/* * At the end of migration, undo the effects of init_range * opaque should be the MIS. @@ -506,20 +480,6 @@ static int cleanup_range(RAMBlock *rb, void *opaque)return 0 ; } -/* -* Initialise postcopy-ram, setting the RAM to a state where we can go into -* postcopy later; must be called prior to any precopy. -* called from arch_init's similarly named ram_postcopy_incoming_init -*/ -int postcopy_ram_incoming_init (MigrationIncomingState *mis) -{ -if (foreach_not_ignored_block (init_range,NULL )) { -return -1 ; - } - -return 0 ; -} -/* * Manage a single vote to the QEMU balloon inhibitor for all postcopy usage, * last caller wins. @@ -1282,12 +1242,6 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis)return false; } -int postcopy_ram_incoming_init (MigrationIncomingState *mis) -{ -error_report ("postcopy_ram_incoming_init: No OS support" ); -return -1 ; -} -int postcopy_ram_incoming_cleanup (MigrationIncomingState *mis) {assert (0 );migration/postcopy-ram.h +0
-7@@ -22,13 +22,6 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis);*/ int postcopy_ram_incoming_setup (MigrationIncomingState *mis); -/* -* Initialise postcopy-ram, setting the RAM to a state where we can go into -* postcopy later; must be called prior to any precopy. -* called from ram.c's similarly named ram_postcopy_incoming_init -*/ -int postcopy_ram_incoming_init (MigrationIncomingState *mis); -/* * At the end of a migration where postcopy_ram_incoming_init was called. */ migration/ram.c +0
-16@@ -4015,22 +4015,6 @@ static int ram_load_cleanup(void *opaque)return 0 ; } -/** -* ram_postcopy_incoming_init: allocate postcopy data structures -* -* Returns 0 for success and negative if there was one error -* -* @mis: current migration incoming state -* -* Allocate data structures etc needed by incoming migration with -* postcopy-ram. postcopy-ram's similarly names -* postcopy_ram_incoming_init does the work. -*/ -int ram_postcopy_incoming_init (MigrationIncomingState *mis) -{ -return postcopy_ram_incoming_init (mis); -} -/** * ram_load_postcopy: load a page in postcopy case * migration/ram.h +0
-1@@ -58,7 +58,6 @@ void ram_postcopy_migrated_memory_release(MigrationState *ms);int ram_postcopy_send_discard_bitmap (MigrationState *ms);/* For incoming postcopy discard */ int ram_discard_range (const char *block_name,uint64_t start,size_t length); -int ram_postcopy_incoming_init (MigrationIncomingState *mis);bool postcopy_is_running (void );void ram_handle_compressed (void *host,uint8_t ch,uint64_t size);migration/savevm.c +0
-4@@ -1674,10 +1674,6 @@ static int loadvm_postcopy_handle_advise(MigrationIncomingState *mis,return -1 ; } -if (ram_postcopy_incoming_init (mis)) { -return -1 ; - } -return 0 ; }Signature · 1 line
2.17.1
Signature · 2 lines
Wei Yang Help you, Help me
Hi, David and Juan
Does it look good to you?
Quoted 165 lines · Wei Yang
ram_discard_range()unmap page for specific range. To be specific, this clears related page table entries so that userfault would be triggered. But this step is not necessary at the very beginning.
ram_postcopy_incoming_init()is called when destination gets ADVISE command. ADVISE command is sent when migration thread just starts, which implies destination is not running yet. This means no page fault happened and memory region's page tables entries are empty.This patch removes the discard at the beginning.
Signed-off-by Wei Yang <[email protected]>---
migration/postcopy-ram.c | 46 ---------------------------------------- migration/postcopy-ram.h | 7 ------ migration/ram.c | 16 -------------- migration/ram.h | 1 - migration/savevm.c | 4 ---- 5 files changed, 74 deletions(-)migration/postcopy-ram.c +0
-46@@ -443,32 +443,6 @@ out:return ret; } -/* -* Setup an area of RAM so that it *can* be used for postcopy later; this -* must be done right at the start prior to pre-copy. -* opaque should be the MIS. -*/ -static int init_range (RAMBlock *rb,void *opaque) -{ -const char *block_name =qemu_ram_get_idstr (rb); -void *host_addr =qemu_ram_get_host_addr (rb); -ram_addr_t offset =qemu_ram_get_offset (rb); -ram_addr_t length =qemu_ram_get_used_length (rb); -trace_postcopy_init_range (block_name, host_addr, offset, length); - -/* -* We need the whole of RAM to be truly empty for postcopy, so things -* like ROMs and any data tables built during init must be zero'd -* - we're going to get the copy from the source anyway. -* (Precopy will just overwrite this data, so doesn't need the discard) -*/ -if (ram_discard_range (block_name,0 , length)) { -return -1 ; - } - -return 0 ; -} -/* * At the end of migration, undo the effects of init_range * opaque should be the MIS. @@ -506,20 +480,6 @@ static int cleanup_range(RAMBlock *rb, void *opaque)return 0 ; } -/* -* Initialise postcopy-ram, setting the RAM to a state where we can go into -* postcopy later; must be called prior to any precopy. -* called from arch_init's similarly named ram_postcopy_incoming_init -*/ -int postcopy_ram_incoming_init (MigrationIncomingState *mis) -{ -if (foreach_not_ignored_block (init_range,NULL )) { -return -1 ; - } - -return 0 ; -} -/* * Manage a single vote to the QEMU balloon inhibitor for all postcopy usage, * last caller wins. @@ -1282,12 +1242,6 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis)return false; } -int postcopy_ram_incoming_init (MigrationIncomingState *mis) -{ -error_report ("postcopy_ram_incoming_init: No OS support" ); -return -1 ; -} -int postcopy_ram_incoming_cleanup (MigrationIncomingState *mis) {assert (0 );migration/postcopy-ram.h +0
-7@@ -22,13 +22,6 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis);*/ int postcopy_ram_incoming_setup (MigrationIncomingState *mis); -/* -* Initialise postcopy-ram, setting the RAM to a state where we can go into -* postcopy later; must be called prior to any precopy. -* called from ram.c's similarly named ram_postcopy_incoming_init -*/ -int postcopy_ram_incoming_init (MigrationIncomingState *mis); -/* * At the end of a migration where postcopy_ram_incoming_init was called. */ migration/ram.c +0
-16@@ -4015,22 +4015,6 @@ static int ram_load_cleanup(void *opaque)return 0 ; } -/** -* ram_postcopy_incoming_init: allocate postcopy data structures -* -* Returns 0 for success and negative if there was one error -* -* @mis: current migration incoming state -* -* Allocate data structures etc needed by incoming migration with -* postcopy-ram. postcopy-ram's similarly names -* postcopy_ram_incoming_init does the work. -*/ -int ram_postcopy_incoming_init (MigrationIncomingState *mis) -{ -return postcopy_ram_incoming_init (mis); -} -/** * ram_load_postcopy: load a page in postcopy case * migration/ram.h +0
-1@@ -58,7 +58,6 @@ void ram_postcopy_migrated_memory_release(MigrationState *ms);int ram_postcopy_send_discard_bitmap (MigrationState *ms);/* For incoming postcopy discard */ int ram_discard_range (const char *block_name,uint64_t start,size_t length); -int ram_postcopy_incoming_init (MigrationIncomingState *mis);bool postcopy_is_running (void );void ram_handle_compressed (void *host,uint8_t ch,uint64_t size);migration/savevm.c +0
-4@@ -1674,10 +1674,6 @@ static int loadvm_postcopy_handle_advise(MigrationIncomingState *mis,return -1 ; } -if (ram_postcopy_incoming_init (mis)) { -return -1 ; - } -return 0 ; }Signature · 1 line
2.17.1
Signature · 2 lines
Wei Yang Help you, Help me
Quoted 37 lines · * Wei Yang ([email protected]) wrote:
ram_discard_range()unmap page for specific range. To be specific, this clears related page table entries so that userfault would be triggered. But this step is not necessary at the very beginning.
ram_postcopy_incoming_init()is called when destination gets ADVISE command. ADVISE command is sent when migration thread just starts, which implies destination is not running yet. This means no page fault happened and memory region's page tables entries are empty.This patch removes the discard at the beginning.
Signed-off-by Wei Yang <[email protected]>--- migration/postcopy-ram.c | 46 ---------------------------------------- migration/postcopy-ram.h | 7 ------ migration/ram.c | 16 -------------- migration/ram.h | 1 - migration/savevm.c | 4 ---- 5 files changed, 74 deletions(-)migration/postcopy-ram.c +0
-9@@ -443,32 +443,6 @@ out:return ret; } -/* -* Setup an area of RAM so that it *can* be used for postcopy later; this -* must be done right at the start prior to pre-copy. -* opaque should be the MIS. -*/ -static int init_range (RAMBlock *rb,void *opaque) -{ -const char *block_name =qemu_ram_get_idstr (rb); -void *host_addr =qemu_ram_get_host_addr (rb);
migration/postcopy-ram.c out: · line 464
Quoted 10 lines
migration/postcopy-ram.c +0
-10-ram_addr_t offset =qemu_ram_get_offset (rb); -ram_addr_t length =qemu_ram_get_used_length (rb); -trace_postcopy_init_range (block_name, host_addr, offset, length); - -/* -* We need the whole of RAM to be truly empty for postcopy, so things -* like ROMs and any data tables built during init must be zero'd -* - we're going to get the copy from the source anyway. -* (Precopy will just overwrite this data, so doesn't need the discard) -*/
But this comment explains why we want to do the discard; we want to make sure that any memory that's been populated by the destination during the init process is discarded and replaced by content from the source.
Dave
Quoted 119 lines
migration/postcopy-ram.c +0
-27-if (ram_discard_range (block_name,0 , length)) { -return -1 ; - } - -return 0 ; -} -/* * At the end of migration, undo the effects of init_range * opaque should be the MIS. @@ -506,20 +480,6 @@ static int cleanup_range(RAMBlock *rb, void *opaque)return 0 ; } -/* -* Initialise postcopy-ram, setting the RAM to a state where we can go into -* postcopy later; must be called prior to any precopy. -* called from arch_init's similarly named ram_postcopy_incoming_init -*/ -int postcopy_ram_incoming_init (MigrationIncomingState *mis) -{ -if (foreach_not_ignored_block (init_range,NULL )) { -return -1 ; - } - -return 0 ; -} -/* * Manage a single vote to the QEMU balloon inhibitor for all postcopy usage, * last caller wins. @@ -1282,12 +1242,6 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis)return false; } -int postcopy_ram_incoming_init (MigrationIncomingState *mis) -{ -error_report ("postcopy_ram_incoming_init: No OS support" ); -return -1 ; -} -int postcopy_ram_incoming_cleanup (MigrationIncomingState *mis) {assert (0 );migration/postcopy-ram.h +0
-7@@ -22,13 +22,6 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis);*/ int postcopy_ram_incoming_setup (MigrationIncomingState *mis); -/* -* Initialise postcopy-ram, setting the RAM to a state where we can go into -* postcopy later; must be called prior to any precopy. -* called from ram.c's similarly named ram_postcopy_incoming_init -*/ -int postcopy_ram_incoming_init (MigrationIncomingState *mis); -/* * At the end of a migration where postcopy_ram_incoming_init was called. */ migration/ram.c +0
-16@@ -4015,22 +4015,6 @@ static int ram_load_cleanup(void *opaque)return 0 ; } -/** -* ram_postcopy_incoming_init: allocate postcopy data structures -* -* Returns 0 for success and negative if there was one error -* -* @mis: current migration incoming state -* -* Allocate data structures etc needed by incoming migration with -* postcopy-ram. postcopy-ram's similarly names -* postcopy_ram_incoming_init does the work. -*/ -int ram_postcopy_incoming_init (MigrationIncomingState *mis) -{ -return postcopy_ram_incoming_init (mis); -} -/** * ram_load_postcopy: load a page in postcopy case * migration/ram.h +0
-1@@ -58,7 +58,6 @@ void ram_postcopy_migrated_memory_release(MigrationState *ms);int ram_postcopy_send_discard_bitmap (MigrationState *ms);/* For incoming postcopy discard */ int ram_discard_range (const char *block_name,uint64_t start,size_t length); -int ram_postcopy_incoming_init (MigrationIncomingState *mis);bool postcopy_is_running (void );void ram_handle_compressed (void *host,uint8_t ch,uint64_t size);migration/savevm.c +0
-4@@ -1674,10 +1674,6 @@ static int loadvm_postcopy_handle_advise(MigrationIncomingState *mis,return -1 ; } -if (ram_postcopy_incoming_init (mis)) { -return -1 ; - } -return 0 ; }Signature · 1 line
2.17.1
--
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 44 lines · Dr. David Alan Gilbert
Quoted 43 lines · * Wei Yang ([email protected]) wrote:
ram_discard_range()unmap page for specific range. To be specific, this clears related page table entries so that userfault would be triggered. But this step is not necessary at the very beginning.
ram_postcopy_incoming_init()is called when destination gets ADVISE command. ADVISE command is sent when migration thread just starts, which implies destination is not running yet. This means no page fault happened and memory region's page tables entries are empty.This patch removes the discard at the beginning.
Signed-off-by Wei Yang <[email protected]>--- migration/postcopy-ram.c | 46 ---------------------------------------- migration/postcopy-ram.h | 7 ------ migration/ram.c | 16 -------------- migration/ram.h | 1 - migration/savevm.c | 4 ---- 5 files changed, 74 deletions(-)migration/postcopy-ram.c +0
-15@@ -443,32 +443,6 @@ out:return ret; } -/* -* Setup an area of RAM so that it *can* be used for postcopy later; this -* must be done right at the start prior to pre-copy. -* opaque should be the MIS. -*/ -static int init_range (RAMBlock *rb,void *opaque) -{ -const char *block_name =qemu_ram_get_idstr (rb); -void *host_addr =qemu_ram_get_host_addr (rb); -ram_addr_t offset =qemu_ram_get_offset (rb); -ram_addr_t length =qemu_ram_get_used_length (rb); -trace_postcopy_init_range (block_name, host_addr, offset, length); - -/* -* We need the whole of RAM to be truly empty for postcopy, so things
Quoted 9 lines
migration/postcopy-ram.c out: · line 464
Quoted 4 lines
migration/postcopy-ram.c +0
-4-* like ROMs and any data tables built during init must be zero'd -* - we're going to get the copy from the source anyway. -* (Precopy will just overwrite this data, so doesn't need the discard) -*/ But this comment explains why we want to do the discard; we want to make sure that any memory that's been populated by the destination during the init process is discarded and replaced by content from the source.
OK, you are right. I missed the init stage.
Quoted 2 lines
Dave
Signature · 2 lines
Wei Yang Help you, Help me