Hi Marc,
On 9/29/22 10:42 PM, Marc Zyngier wrote:
On Thu, 29 Sep 2022 10:50:12 +0100,
Gavin Shan <gshan@xxxxxxxxxx> wrote:
On 9/29/22 12:52 AM, Peter Xu wrote:
On Wed, Sep 28, 2022 at 09:25:34AM +0100, Marc Zyngier wrote:
On Wed, 28 Sep 2022 00:47:43 +0100,
Gavin Shan <gshan@xxxxxxxxxx> wrote:
I have rough idea as below. It's appreciated if you can comment before I'm
going a head for the prototype. The overall idea is to introduce another
dirty ring for KVM (kvm-dirty-ring). It's updated and visited separately
to dirty ring for vcpu (vcpu-dirty-ring).
- When the various VGIC/ITS table base addresses are specified, kvm-dirty-ring
entries are added to mark those pages as 'always-dirty'. In mark_page_dirty_in_slot(),
those 'always-dirty' pages will be skipped, no entries pushed to vcpu-dirty-ring.
- Similar to vcpu-dirty-ring, kvm-dirty-ring is accessed from userspace through
mmap(kvm->fd). However, there won't have similar reset interface. It means
'struct kvm_dirty_gfn::flags' won't track any information as we do for
vcpu-dirty-ring. In this regard, kvm-dirty-ring is purely shared buffer to
advertise 'always-dirty' pages from host to userspace.
- For QEMU, shutdown/suspend/resume cases won't be concerning
us any more. The
only concerned case is migration. When the migration is about to complete,
kvm-dirty-ring entries are fetched and the dirty bits are updated to global
dirty page bitmap and RAMBlock's dirty page bitmap. For this, I'm still reading
the code to find the best spot to do it.
I think it makes a lot of sense to have a way to log writes that are
not generated by a vpcu, such as the GIC and maybe other things in the
future, such as DMA traffic (some SMMUs are able to track dirty pages
as well).
However, I don't really see the point in inventing a new mechanism for
that. Why don't we simply allow non-vpcu dirty pages to be tracked in
the dirty *bitmap*?
From a kernel perspective, this is dead easy:
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index 5b064dbadaf4..ae9138f29d51 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -3305,7 +3305,7 @@ void mark_page_dirty_in_slot(struct kvm *kvm,
struct kvm_vcpu *vcpu = kvm_get_running_vcpu();
#ifdef CONFIG_HAVE_KVM_DIRTY_RING
- if (WARN_ON_ONCE(!vcpu) || WARN_ON_ONCE(vcpu->kvm != kvm))
+ if (WARN_ON_ONCE(vcpu && vcpu->kvm != kvm))
return;
#endif
@@ -3313,10 +3313,11 @@ void mark_page_dirty_in_slot(struct kvm
*kvm,
unsigned long rel_gfn = gfn - memslot->base_gfn;
u32 slot = (memslot->as_id << 16) | memslot->id;
- if (kvm->dirty_ring_size)
+ if (vpcu && kvm->dirty_ring_size)
kvm_dirty_ring_push(&vcpu->dirty_ring,
slot, rel_gfn);
- else
+ /* non-vpcu dirtying ends up in the global bitmap */
+ if (!vcpu && memslot->dirty_bitmap)
set_bit_le(rel_gfn, memslot->dirty_bitmap);
}
}
though I'm sure there is a few more things to it.
Yes, currently the bitmaps are not created when rings are enabled.
kvm_prepare_memory_region() has:
else if (!kvm->dirty_ring_size) {
r = kvm_alloc_dirty_bitmap(new);
But I think maybe that's a solution worth considering. Using the rings
have a major challenge on the limitation of ring size, so that for e.g. an
ioctl we need to make sure the pages to dirty within an ioctl procedure
will not be more than the ring can take. Using dirty bitmap for a last
phase sync of constant (but still very small amount of) dirty pages does
sound reasonable and can avoid that complexity. The payoff is we'll need
to allocate both the rings and the bitmaps.
Ok. I was thinking of using the bitmap to convey the dirty pages for
this particular case, where we don't have running vcpu. The concern I had
is the natural difference between a ring and bitmap. The ring-buffer is
discrete, comparing to bitmap. Besides, it sounds a little strange to
have two different sets of meta-data to track the data (dirty pages).
The problem is that the dirty ring mechanism is a bit blinkered, and
cannot consider a source of dirty pages other than from the vcpus.
Ok.
However, bitmap is easier way than per-vm ring. The constrains with
per-vm ring is just as Peter pointed. So lets reuse the bitmap to
convey the dirty pages for this particular case. I think the payoff,
extra bitmap, is acceptable. For this, we need another capability
(KVM_CAP_DIRTY_LOG_RING_BITMAP?) so that QEMU can collects the dirty
bitmap in the last phase of migration.
Why another capability? Just allowing dirty logging to be enabled
before we saving the GIC state should be enough, shouldn't it?
The GIC state would be just one case where no vcpu can be used to push
dirty page information. As you mentioned, SMMMU HTTU feature could possibly
be another case to ARM64. It's uncertain about other architectures where
dirty-ring will be supported. In QEMU, the dirty (bitmap) logging is enabled
at the beginning of migration and the bitmap is synchronized to global
dirty bitmap and RAMBlock's dirty bitmap gradually, as the following
backtrace shows. What we need to do for QEMU is probably retrieve the
bitmap at point (A).
Without the new capability, we will have to rely on the return value
from ioctls KVM_GET_DIRTY_LOG and KVM_CLEAR_DIRTY_LOG to detect the
capability. For example, -ENXIO is returned on old kernels.
migration_thread
qemu_savevm_state_setup
ram_save_setup
ram_init_all
ram_init_bitmaps
memory_global_dirty_log_start(GLOBAL_DIRTY_MIGRATION) // dirty logging enabled
migration_bitmap_sync_precopy(rs)
:
migration_iteration_run // iteration 0
qemu_savevm_state_pending
migration_bitmap_sync_precopy
qemu_savevm_state_iterate
ram_save_iterate
migration_iteration_run // iteration 1
qemu_savevm_state_pending
migration_bitmap_sync_precopy
qemu_savevm_state_iterate
ram_save_iterate
migration_iteration_run // iteration 2
qemu_savevm_state_pending
migration_bitmap_sync_precopy
qemu_savevm_state_iterate
ram_save_iterate
:
migration_iteration_run // iteration N
qemu_savevm_state_pending
migration_bitmap_sync_precopy
migration_completion
qemu_savevm_state_complete_precopy
qemu_savevm_state_complete_precopy_iterable
ram_save_complete
migration_bitmap_sync_precopy // A
<send all dirty pages>
Note: for post-copy and snapshot, I assume we need to save the dirty bitmap
in the last synchronization, right after the VM is stopped.
If all of us agree on this, I can send another kernel patch to address
this. QEMU still need more patches so that the feature can be supported.
Yes, this will also need some work.
To me, this is just a relaxation of an arbitrary limitation, as the
current assumption that only vcpus can dirty memory doesn't hold at
all.
The initial dirty ring proposal has a per-vm ring, but after we
investigated x86 we found that all legal dirty paths are with a vcpu
context (except one outlier on kvmgt which fixed within itself), so we
dropped the per-vm ring.
One thing to mention is that DMAs should not count in this case because
that's from device perspective, IOW either IOMMU or SMMU dirty tracking
should be reported to the device driver that interacts with the userspace
not from KVM interfaces (e.g. vfio with VFIO_IOMMU_DIRTY_PAGES). That even
includes emulated DMA like vhost (VHOST_SET_LOG_BASE).
Thanks to Peter for mentioning the per-vm ring's history. As I said above,
lets use bitmap instead if all of us agree.
If I'm correct, Marc may be talking about SMMU, which is emulated in host
instead of QEMU. In this case, the DMA target pages are similar to those
pages for vgic/its tables. Both sets of pages are invisible from QEMU.
No, I'm talking about an actual HW SMMU using the HTTU feature that
set the Dirty bit in the PTEs. And people have been working on sharing
SMMU and CPU PTs for some time, which would give us the one true
source of dirty page.
In this configuration, the dirty ring mechanism will be pretty useless.
Ok. I don't know the details. Marc, the dirty bitmap is helpful in this case?
Thanks,
Gavin
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
