migration/ram: background snapshot fixes and optimiations
Status from this message: Queued on my tree.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | migration/ram: Fix populate_read_range()migration/ | +3 | 1 reply | |
| 2/5 | migration/ram: Fix error handling in ram_write_tracking_start()migration/ | +3 | 1 reply | |
| 3/5 | migration/ram: Don't explicitly unprotect when unregistering uffd-wpmigration/ | +0 | 1 reply | |
| 4/5 | migration/ram: Rely on used_length for uffd_change_protection()migration/ | +1 | 1 reply | |
| 5/5 | migration/ram: Optimize ram_write_tracking_start() for RamDiscardManagermigration/ | +34 | 1 reply |
Reviews trailers per patch
All 5 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Peter Xu | Juan Quintela |
|---|---|---|
| Series | A-b | |
| 1/5 | R-b | |
| 2/5 | R-b | |
| 3/5 | R-b | |
| 4/5 | R-b | |
| 5/5 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v1 0/5] migration/ram: background snapshot fixes and optimiations
Playing with background snapshots in combination with hugetlb and virtio-mem, I found two issues and some reasonable optimizations (skip unprotecting when unregistering).
With virtio-mem (RamDiscardManager), we now won't be allocating unnecessary page tables for unplugged ranges when using uffd-wp with shmem/hugetlb.
David Hildenbrand (5):
migration/ram: Fix populate_read_range()
migration/ram: Fix error handling in ram_write_tracking_start() migration/ram: Don't explicitly unprotect when unregistering uffd-wp migration/ram: Rely on used_length for uffd_change_protection() migration/ram: Optimize ram_write_tracking_start() for
RamDiscardManager
migration/ram.c | 54 ++++++++++++++++++++++++++++++++++++------------- 1 file changed, 40 insertions(+), 14 deletions(-)
Signature · 1 line
2.39.0