[v7,0/5] migration: UFFD write-tracking migration/snapshots

Message

Andrey Gruzdev Dec. 17, 2020, 1:04 p.m. UTC

This patch series is a kind of 'rethinking' of Denis Plotnikov's ideas he's
implemented in his series '[PATCH v0 0/4] migration: add background snapshot'.

Currently the only way to make (external) live VM snapshot is using existing
dirty page logging migration mechanism. The main problem is that it tends to
produce a lot of page duplicates while running VM goes on updating already
saved pages. That leads to the fact that vmstate image size is commonly several
times bigger then non-zero part of virtual machine's RSS. Time required to
converge RAM migration and the size of snapshot image severely depend on the
guest memory write rate, sometimes resulting in unacceptably long snapshot
creation time and huge image size.

This series propose a way to solve the aforementioned problems. This is done
by using different RAM migration mechanism based on UFFD write protection
management introduced in v5.7 kernel. The migration strategy is to 'freeze'
guest RAM content using write-protection and iteratively release protection
for memory ranges that have already been saved to the migration stream.
At the same time we read in pending UFFD write fault events and save those
pages out-of-order with higher priority.

How to use:
1. Enable write-tracking migration capability
   virsh qemu-monitor-command <domain> --hmp migrate_set_capability.
track-writes-ram on

2. Start the external migration to a file
   virsh qemu-monitor-command <domain> --hmp migrate exec:'cat > ./vm_state'

3. Wait for the migration finish and check that the migration has completed.
state.


Changes v6->v7:

* 1. Fixed background snapshot on suspended guest: call qemu_system_wakeup_request()
*    before stopping VM to make runstate transition valid.
* 2. Disabled dirty page logging and log syn when 'background-snapshot' is enabled.
* 3. Introduced 'userfaultfd-wrlat.py' script to analyze UFFD write fault latencies.

Changes v5->v6:

* 1. Consider possible hot pluggin/unpluggin of memory device - don't use static
*    for write-tracking support level in migrate_query_write_tracking(), check
*    each time when one tries to enable 'background-snapshot' capability.

Changes v4->v5:

* 1. Refactored util/userfaultfd.c code to support features required by postcopy.
* 2. Introduced checks for host kernel and guest memory backend compatibility
*    to 'background-snapshot' branch in migrate_caps_check().
* 3. Switched to using trace_xxx instead of info_report()/error_report() for
*    cases when error message must be hidden (probing UFFD-IO) or info may be
*    really littering output if goes to stderr.
* 4  Added RCU_READ_LOCK_GUARDs to the code dealing with RAM block list.
* 5. Added memory_region_ref() for each RAM block being wr-protected.
* 6. Reused qemu_ram_block_from_host() instead of custom RAM block lookup routine.
* 7. Refused from using specific hwaddr/ram_addr_t in favour of void */uint64_t.
* 8. Currently dropped 'linear-scan-rate-limiting' patch. The reason is that
*    that choosen criteria for high-latency fault detection (i.e. timestamp of
*    UFFD event fetch) is not representative enough for this task.
*    At the moment it looks somehow like premature optimization effort.
* 8. Dropped some unnecessary/unused code.


Andrey Gruzdev (5):
  migration: introduce 'background-snapshot' migration capability
  migration: introduce UFFD-WP low-level interface helpers
  migration: support UFFD write fault processing in ram_save_iterate()
  migration: implementation of background snapshot thread
  migration: introduce 'userfaultfd-wrlat.py' script

 include/exec/memory.h        |   8 +
 include/qemu/userfaultfd.h   |  35 ++++
 migration/migration.c        | 365 ++++++++++++++++++++++++++++++++++-
 migration/migration.h        |   4 +
 migration/ram.c              | 288 ++++++++++++++++++++++++++-
 migration/ram.h              |   6 +
 migration/savevm.c           |   1 -
 migration/savevm.h           |   2 +
 migration/trace-events       |   2 +
 qapi/migration.json          |   7 +-
 scripts/userfaultfd-wrlat.py | 148 ++++++++++++++
 util/meson.build             |   1 +
 util/trace-events            |   9 +
 util/userfaultfd.c           | 345 +++++++++++++++++++++++++++++++++
 14 files changed, 1211 insertions(+), 10 deletions(-)
 create mode 100644 include/qemu/userfaultfd.h
 create mode 100755 scripts/userfaultfd-wrlat.py
 create mode 100644 util/userfaultfd.c

Comments

[e-mail] Dec. 17, 2020, 2:03 p.m. UTC | #1

Patchew URL: https://patchew.org/QEMU/[e-mail]/



Hi,

This series seems to have some coding style problems. See output below for
more information:

Type: series
Message-id: [e-mail]
Subject: [PATCH v7 0/5] migration: UFFD write-tracking migration/snapshots

=== TEST SCRIPT BEGIN ===
#!/bin/bash
git rev-parse base > /dev/null || exit 0
git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram
./scripts/checkpatch.pl --mailback base..
=== TEST SCRIPT END ===

Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
From https://github.com/patchew-project/qemu
 * [new tag]         patchew/[e-mail] -> patchew/[e-mail]
 - [tag update]      patchew/[e-mail] -> patchew/[e-mail]
Switched to a new branch 'test'
9ee702f migration: introduce 'userfaultfd-wrlat.py' script
2977b12 migration: implementation of background snapshot thread
5e91517 migration: support UFFD write fault processing in ram_save_iterate()
39885b4 migration: introduce UFFD-WP low-level interface helpers
5af2e3b migration: introduce 'background-snapshot' migration capability

=== OUTPUT BEGIN ===
1/5 Checking commit 5af2e3b78ed0 (migration: introduce 'background-snapshot' migration capability)
WARNING: line over 80 characters
#115: FILE: migration/migration.c:1225:
+            error_setg(errp, "Background-snapshot is not supported by host kernel");

WARNING: Block comments use a leading /* on a separate line
#192: FILE: migration/ram.c:3791:
+/* ram_write_tracking_available: check if kernel supports required UFFD features

WARNING: Block comments use a leading /* on a separate line
#202: FILE: migration/ram.c:3801:
+/* ram_write_tracking_compatible: check if guest configuration is

total: 0 errors, 3 warnings, 207 lines checked

Patch 1/5 has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
2/5 Checking commit 39885b4d0da1 (migration: introduce UFFD-WP low-level interface helpers)
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#28: 
new file mode 100644

WARNING: line over 80 characters
#265: FILE: util/userfaultfd.c:163:
+ * uffd_change_protection: protect/un-protect memory range for writes via UFFD-IO

WARNING: line over 80 characters
#324: FILE: util/userfaultfd.c:222:
+        error_report("uffd_copy_page() failed: dst_addr=%p src_addr=%p length=%" PRIu64

WARNING: line over 80 characters
#364: FILE: util/userfaultfd.c:262:
+ * uffd_wakeup: wake up threads waiting on page UFFD-managed page fault resolution

WARNING: line over 80 characters
#385: FILE: util/userfaultfd.c:283:
+        error_report("uffd_wakeup() failed: addr=%p length=%" PRIu64 " errno=%i",

total: 0 errors, 5 warnings, 406 lines checked

Patch 2/5 has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
3/5 Checking commit 5e91517382d9 (migration: support UFFD write fault processing in ram_save_iterate())
WARNING: line over 80 characters
#168: FILE: migration/ram.c:1839:
+        /* We don't want to override existing error from ram_save_host_page(). */

WARNING: Block comments use a leading /* on a separate line
#202: FILE: migration/ram.c:1987:
+        /* caller have hold iothread lock or is in a bh, so there is

WARNING: line over 80 characters
#331: FILE: migration/ram.c:4009:
+    error_report("ram_write_tracking_start() failed: restoring initial memory state");

WARNING: line over 80 characters
#341: FILE: migration/ram.c:4019:
+        uffd_change_protection(rs->uffdio_fd, bs->host, bs->max_length, false, false);

WARNING: line over 80 characters
#370: FILE: migration/ram.c:4048:
+        uffd_change_protection(rs->uffdio_fd, bs->host, bs->max_length, false, false);

total: 0 errors, 5 warnings, 361 lines checked

Patch 3/5 has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
4/5 Checking commit 2977b123ecbd (migration: implementation of background snapshot thread)
WARNING: line over 80 characters
#156: FILE: migration/migration.c:3810:
+ * mechanism, which effectively results in that saved snapshot is the state of VM

total: 0 errors, 1 warnings, 330 lines checked

Patch 4/5 has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
5/5 Checking commit 9ee702f9344f (migration: introduce 'userfaultfd-wrlat.py' script)
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#13: 
new file mode 100755

ERROR: please use python3 interpreter
#18: FILE: scripts/userfaultfd-wrlat.py:1:
+#!/usr/bin/python

ERROR: trailing whitespace
#113: FILE: scripts/userfaultfd-wrlat.py:96:
+     * or pending signal we'll still get (at least for v5.8.0 kernel) $

ERROR: trailing whitespace
#116: FILE: scripts/userfaultfd-wrlat.py:99:
+     * keeping initial timestamp unchanged for the faulting thread.  $

WARNING: line over 80 characters
#144: FILE: scripts/userfaultfd-wrlat.py:127:
+b.attach_kretprobe(event="handle_userfault", fn_name="retprobe_handle_userfault")

total: 3 errors, 2 warnings, 148 lines checked

Patch 5/5 has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.

=== OUTPUT END ===

Test command exited with code: 1


The full log is available at
http://patchew.org/logs/[e-mail]/testing.checkpatch/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to [e-mail]