Gavin Shan 856e23a0fb kvm: Enable dirty ring for arm64 ... arm64 has different capability from x86 to enable the dirty ring, which is KVM_CAP_DIRTY_LOG_RING_ACQ_REL. Besides, arm64 also needs the backup bitmap extension (KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP) when 'kvm-arm-gicv3' or 'arm-its-kvm' device is enabled. Here the extension is always enabled and the unnecessary overhead to do the last stage of dirty log synchronization when those two devices aren't used is introduced, but the overhead should be very small and acceptable. The benefit is cover future cases where those two devices are used without modifying the code. Signed-off-by: Gavin Shan <gshan@redhat.com> Reviewed-by: Juan Quintela <quintela@redhat.com> Tested-by: Zhenyu Zhang <zhenyzha@redhat.com> Reviewed-by: Peter Xu <peterx@redhat.com> Message-Id: <20230509022122.20888-5-gshan@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2023-05-18 08:53:51 +02:00
..
kvm-accel-ops.c	gdbstub: move update guest debug to accel ops	2023-03-07 20:44:09 +00:00
kvm-all.c	kvm: Enable dirty ring for arm64	2023-05-18 08:53:51 +02:00
kvm-cpus.h	gdbstub: Use vaddr type for generic insert/remove_breakpoint() API	2023-02-27 22:29:01 +01:00
meson.build
trace-events
trace.h