Re: [PATCH 1/2] migration: Implement dirty ring

I apologize for implementing this without knowledge of QEMU's policy. I will remove this option and instead implement it using migrate_set_parameter or migrate_set_capability. Is this approach acceptable? This is my first time contributing to QEMU, so I appreciate your guidance. Thank you and

[PATCH 1/2] migration: Implement dirty ring

r specify nothing or "-migration dirty-logging=bitmap". If the dirty ring becomes full, it falls back to the bitmap for that round. Signed-off-by: Shota Imamura --- accel/kvm/kvm-all.c| 36 - include/exec/ram_addr.h| 131 +++-- includ

[PATCH 2/2] qtest/migration: Add dirty ring tests

This commit adds tests for migration using the dirty ring. To avoid confusion with KVM's dirty ring, use_dirty_ring has been changed to use_kvm_dirty_ring, and use_qemu_dirty_ring has been added. Signed-off-by: Shota Imamura --- tests/qtest/migration-test.c

[PATCH 0/2] Implement dirty ring for pre-copy migration

This patch series introduces the dirty ring as an additional method for dirty tracking, alongside the existing dirty bitmap. Shota Imamura (2): migration: Implement dirty ring qtest/migration: Add dirty ring tests accel/kvm/kvm-all.c| 36 - include/exec/ram_addr.h