In order to differenciate between architectures that require no extra synchronisation when accessing the dirty ring and those who do, add a new capability (KVM_CAP_DIRTY_LOG_RING_ACQ_REL) that identify the latter sort. TSO architectures can obviously advertise both, while relaxed architectures must only advertise the ACQ_REL version. This requires some configuration symbol rejigging, with HAVE_KVM_DIRTY_RING being only indirectly selected by two top-level config symbols: - HAVE_KVM_DIRTY_RING_TSO for strongly ordered architectures (x86) - HAVE_KVM_DIRTY_RING_ACQ_REL for weakly ordered architectures (arm64)
Showing the changes to include/uapi (1 of 4 files). Show all
Unified · Split
| @@ -1177,6 +1177,7 @@ struct kvm_ppc_resize_hpt { · 1176 unmodified lines | |||
| 1177 | #define KVM_CAP_VM_DISABLE_NX_HUGE_PAGES 220 | 1177 | #define KVM_CAP_VM_DISABLE_NX_HUGE_PAGES 220 |
| 1178 | #define KVM_CAP_S390_ZPCI_OP 221 | 1178 | #define KVM_CAP_S390_ZPCI_OP 221 |
| 1179 | #define KVM_CAP_S390_CPU_TOPOLOGY 222 | 1179 | #define KVM_CAP_S390_CPU_TOPOLOGY 222 |
| 1180 | #define KVM_CAP_DIRTY_LOG_RING_ACQ_REL 223 | ||
| 1180 | 1181 | ||
| 1181 | #ifdef KVM_CAP_IRQ_ROUTING | 1182 | #ifdef KVM_CAP_IRQ_ROUTING |
| 1182 | 1183 | ||