Peter Xu b2cc64c4f3 KVM: Make dirty ring exclusive to dirty bitmap log ... There's no good reason to use both the dirty bitmap logging and the new dirty ring buffer to track dirty bits. We should be able to even support both of them at the same time, but it could complicate things which could actually help little. Let's simply make it the rule before we enable dirty ring on any arch, that we don't allow these two interfaces to be used together. The big world switch would be KVM_CAP_DIRTY_LOG_RING capability enablement. That's where we'll switch from the default dirty logging way to the dirty ring way. As long as kvm->dirty_ring_size is setup correctly, we'll once and for all switch to the dirty ring buffer mode for the current virtual machine. Signed-off-by: Peter Xu <peterx@redhat.com> Message-Id: <20201001012224.5818-1-peterx@redhat.com> [Change errno from EINVAL to ENXIO. - Paolo] Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2020-11-15 09:49:16 -05:00
..
kvm	KVM: Make dirty ring exclusive to dirty bitmap log	2020-11-15 09:49:16 -05:00
uml	docs: virt: user_mode_linux_howto_v2.rst: fix a literal block markup	2020-10-16 07:28:20 +02:00
guest-halt-polling.rst	docs: virt: guest-halt-polling.txt convert to ReST	2020-02-12 20:10:08 +01:00
index.rst	Char/Misc driver patches for 5.10-rc1	2020-10-15 10:01:51 -07:00
ne_overview.rst	nitro_enclaves: Add overview documentation	2020-09-22 13:58:41 +02:00
paravirt_ops.rst	Documentation: move Documentation/virtual to Documentation/virt	2019-07-24 10:52:11 +02:00