ARM64 needs to dirty memory outside of a VCPU context when VGIC/ITS is enabled. It's conflicting with that ring-based dirty page tracking always requires a running VCPU context. Introduce a new flavor of dirty ring that requires the use of both VCPU dirty rings and a dirty bitmap. The expectation is that for non-VCPU sources of dirty memory (such as the VGIC/ITS on arm64), KVM writes to the dirty bitmap. Userspace should scan the dirty bitmap before migrating the VM to the target. Use an additional capability to advertise this behavior. The newly added capability (KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP) can't be enabled before KVM_CAP_DIRTY_LOG_RING_ACQ_REL on ARM64. In this way, the newly added capability is treated as an extension of KVM_CAP_DIRTY_LOG_RING_ACQ_REL.
Showing the changes to include/uapi (1 of 8 files). Show all
Unified · Split
| @@ -1178,6 +1178,7 @@ struct kvm_ppc_resize_hpt { · 1177 unmodified lines | ||
| 1178 | 1178 | #define KVM_CAP_S390_ZPCI_OP 221 |
| 1179 | 1179 | #define KVM_CAP_S390_CPU_TOPOLOGY 222 |
| 1180 | 1180 | #define KVM_CAP_DIRTY_LOG_RING_ACQ_REL 223 |
| 1181 | +#define KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP 224 | |
| 1181 | 1182 | |
| 1182 | 1183 | #ifdef KVM_CAP_IRQ_ROUTING |
| 1183 | 1184 | |