On Fri, 04 Nov 2022 23:40:42 +0000,
Gavin Shan <gshan@xxxxxxxxxx> wrote:
>
> This series enables the ring-based dirty memory tracking for ARM64.
> The feature has been available and enabled on x86 for a while. It
> is beneficial when the number of dirty pages is small in a checkpointing
> system or live migration scenario. More details can be found from
> fb04a1eddb1a ("KVM: X86: Implement ring-based dirty memory tracking").
>
> This series is applied to v6.1.rc3, plus commit c227590467cb ("KVM:
> Check KVM_CAP_DIRTY_LOG_{RING, RING_ACQ_REL} prior to enabling them").
> The commit is currently in Marc's 'fixes' branch, targeting v6.1.rc4/5.
This is starting to look good to me, and my only concerns are around
the documentation and the bit of nitpicking on patch 4. If we can
converge quickly on that, I'd like to queue this quickly and leave it
to simmer in -next.
> v7: https://lore.kernel.org/kvmarm/20221031003621.164306-1-gshan@xxxxxxxxxx/
> v6: https://lore.kernel.org/kvmarm/20221011061447.131531-1-gshan@xxxxxxxxxx/
> v5: https://lore.kernel.org/all/20221005004154.83502-1-gshan@xxxxxxxxxx/
> v4: https://lore.kernel.org/kvmarm/20220927005439.21130-1-gshan@xxxxxxxxxx/
> v3: https://lore.kernel.org/r/20220922003214.276736-1-gshan@xxxxxxxxxx
> v2: https://lore.kernel.org/lkml/YyiV%2Fl7O23aw5aaO@xz-m1.local/T/
> v1: https://lore.kernel.org/lkml/20220819005601.198436-1-gshan@xxxxxxxxxx
>
> Testing
> =======
> (1) kvm/selftests/dirty_log_test
> (2) Live migration by QEMU
Could you point to a branch that has the required QEMU changes?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
