Cleanup migration/ram.c
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 17 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | migration/ram.c: start of migration_bitmap_sync_range is always 0migration/ | +4 | 5 replies | |
| 2/3 | migration/ram.c: start of cpu_physical_memory_sync_dirty_bitmap is always 0include/ migration/ | +7 | 6 replies | |
| 3/3 | ram: RAMBlock->offset is always aligned to a wordinclude/ | +9 | 2 replies |
Reviews trailers per patch
1 of 3 patches has a Reviewed-by or Acked-by.
| Patch | Dr. David Alan Gilbert |
|---|---|
| 1/3 | R-b |
| 2/3 | |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
The *start* of migration_bitmap_sync_range is always 0, we can remove this parameter.
Since RAMBlock->offset is always *word* aligned, we can remove the check on offset and simplify the logic a little.
Wei Yang (3):
migration/ram.c: start of migration_bitmap_sync_range is always 0 migration/ram.c: start of cpu_physical_memory_sync_dirty_bitmap is
always 0
ram: RAMBlock->offset is always aligned to a word
include/exec/ram_addr.h | 24 ++++++++++++------------ migration/ram.c | 8 ++++---- 2 files changed, 16 insertions(+), 16 deletions(-)
Signature · 1 line
2.19.1