[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFCv1 7/8] hw/arm/virt: Enable backup bitmap for dirty ring
|
From: |
Juan Quintela |
|
Subject: |
Re: [PATCH RFCv1 7/8] hw/arm/virt: Enable backup bitmap for dirty ring |
|
Date: |
Wed, 08 Feb 2023 23:14:11 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Gavin Shan <gshan@redhat.com> wrote:
> When KVM device "kvm-arm-gicv3" or "arm-its-kvm" is used, we have to
> enable the backup bitmap for the dirty ring. Otherwise, the migration
> will fail because those two devices are using the backup bitmap to track
> dirty guest memory, corresponding to various hardware tables.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
- [PATCH RFCv1 4/8] kvm: Introduce secondary dirty bitmap, (continued)
- [PATCH RFCv1 4/8] kvm: Introduce secondary dirty bitmap, Gavin Shan, 2023/02/06
- [PATCH RFCv1 8/8] kvm: Enable dirty ring for arm64, Gavin Shan, 2023/02/06
- [PATCH RFCv1 6/8] kvm: Add helper kvm_dirty_ring_init(), Gavin Shan, 2023/02/06
- [PATCH RFCv1 5/8] kvm: Synchronize secondary bitmap in last stage, Gavin Shan, 2023/02/06
- [PATCH RFCv1 7/8] hw/arm/virt: Enable backup bitmap for dirty ring, Gavin Shan, 2023/02/06
- Re: [PATCH RFCv1 7/8] hw/arm/virt: Enable backup bitmap for dirty ring,
Juan Quintela <=