On Mon, 31 Oct 2022 08:36:12 +0800, Gavin Shan 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").
>
> 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
>
> [...]
Applied to fixes, thanks!
[3/9] KVM: Check KVM_CAP_DIRTY_LOG_{RING, RING_ACQ_REL} prior to enabling them
commit: 7a2726ec3290c52f52ce8d5f5af73ab8c7681bc1
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
