mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-09-09 08:17:53 -06:00
migration: support UFFD write fault processing in ram_save_iterate()
In this particular implementation the same single migration thread is responsible for both normal linear dirty page migration and procesing UFFD page fault events. Processing write faults includes reading UFFD file descriptor, finding respective RAM block and saving faulting page to the migration stream. After page has been saved, write protection can be removed. Since asynchronous version of qemu_put_buffer() is expected to be used to save pages, we also have to flush migraion stream prior to un-protecting saved memory range. Write protection is being removed for any previously protected memory chunk that has hit the migration stream. That's valid for pages from linear page scan along with write fault pages. Signed-off-by: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com> Acked-by: Peter Xu <peterx@redhat.com> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Message-Id: <20210129101407.103458-4-andrey.gruzdev@virtuozzo.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com> fixup pagefault.address cast for 32bit
This commit is contained in:
parent
0e9b5cd6b2
commit
278e2f551a
4 changed files with 306 additions and 29 deletions
|
@ -150,6 +150,13 @@ typedef struct IOMMUTLBEvent {
|
|||
#define RAM_PMEM (1 << 5)
|
||||
|
||||
|
||||
/*
|
||||
* UFFDIO_WRITEPROTECT is used on this RAMBlock to
|
||||
* support 'write-tracking' migration type.
|
||||
* Implies ram_state->ram_wt_enabled.
|
||||
*/
|
||||
#define RAM_UF_WRITEPROTECT (1 << 6)
|
||||
|
||||
static inline void iommu_notifier_init(IOMMUNotifier *n, IOMMUNotify fn,
|
||||
IOMMUNotifierFlag flags,
|
||||
hwaddr start, hwaddr end,
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue