diff options
| author | Andrey Gruzdev <andrey.gruzdev@virtuozzo.com> | 2021-04-01 12:22:25 +0300 |
|---|---|---|
| committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | 2021-04-07 18:37:28 +0100 |
| commit | eeccb99c9d28484303f721e94c5084e9c29a3d03 (patch) | |
| tree | bdd58066e9701094a592aa2343a8528f7a08a5b2 /migration/ram.h | |
| parent | 1a8e44a89f1976e06300393337f78d561f95b339 (diff) | |
| download | qemu-eeccb99c9d28484303f721e94c5084e9c29a3d03.zip qemu-eeccb99c9d28484303f721e94c5084e9c29a3d03.tar.gz qemu-eeccb99c9d28484303f721e94c5084e9c29a3d03.tar.bz2 | |
migration: Pre-fault memory before starting background snasphot
This commit solves the issue with userfault_fd WP feature that
background snapshot is based on. For any never poluated or discarded
memory page, the UFFDIO_WRITEPROTECT ioctl() would skip updating
PTE for that page, thereby loosing WP setting for it.
So we need to pre-fault pages for each RAM block to be protected
before making a userfault_fd wr-protect ioctl().
Fixes: 278e2f551a095b234de74dca9c214d5502a1f72c (migration: support
UFFD write fault processing in ram_save_iterate())
Signed-off-by: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
Reported-by: David Hildenbrand <david@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Message-Id: <20210401092226.102804-4-andrey.gruzdev@virtuozzo.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
dgilbert:
Bodged ifdef __linux__ on ram_write_tracking_prepare, should really
go in a stub
Diffstat (limited to 'migration/ram.h')
| -rw-r--r-- | migration/ram.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/migration/ram.h b/migration/ram.h index 6378bb3..4833e9f 100644 --- a/migration/ram.h +++ b/migration/ram.h @@ -82,6 +82,7 @@ void colo_incoming_start_dirty_log(void); /* Background snapshot */ bool ram_write_tracking_available(void); bool ram_write_tracking_compatible(void); +void ram_write_tracking_prepare(void); int ram_write_tracking_start(void); void ram_write_tracking_stop(void); |