lkml.org 
[lkml]   [2020]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v8 00/14] KVM: Dirty ring interface
Date
> From: Peter Xu <peterx@redhat.com>
> Sent: Thursday, April 23, 2020 2:52 AM
>
> Hi,
>
> TL;DR: I'm thinking whether we should record pure GPA/GFN instead of
> (slot_id,
> slot_offset) tuple for dirty pages in kvm dirty ring to unbind kvm_dirty_gfn
> with memslots.
>
> (A slightly longer version starts...)
>
> The problem is that binding dirty tracking operations to KVM memslots is a
> restriction that needs synchronization to memslot changes, which further
> needs
> synchronization across all the vcpus because they're the consumers of
> memslots.
> E.g., when we remove a memory slot, we need to flush all the dirty bits
> correctly before we do the removal of the memslot. That's actually an
> known
> defect for QEMU/KVM [1] (I bet it could be a defect for many other
> hypervisors...) right now with current dirty logging. Meanwhile, even if we
> fix it, that procedure is not scale at all, and error prone to dead locks.
>
> Here memory removal is really an (still corner-cased but relatively) important
> scenario to think about for dirty logging comparing to memory additions &
> movings. Because memory addition will always have no initial dirty page,
> and
> we don't really move RAM a lot (or do we ever?!) for a general VM use case.
>
> Then I went a step back to think about why we need these dirty bit
> information
> after all if the memslot is going to be removed?
>
> There're two cases:
>
> - When the memslot is going to be removed forever, then the dirty
> information
> is indeed meaningless and can be dropped, and,
>
> - When the memslot is going to be removed but quickly added back with
> changed
> size, then we need to keep those dirty bits because it's just a commmon
> way
> to e.g. punch an MMIO hole in an existing RAM region (here I'd confess I
> feel like using "slot_id" to identify memslot is really unfriendly syscall
> design for things like "hole punchings" in the RAM address space...
> However such "punch hold" operation is really needed even for a common
> guest for either system reboots or device hotplugs, etc.).

why would device hotplug punch a hole in an existing RAM region?

>
> The real scenario we want to cover for dirty tracking is the 2nd one.
>
> If we can track dirty using raw GPA, the 2nd scenario is solved itself.
> Because we know we'll add those memslots back (though it might be with a
> different slot ID), then the GPA value will still make sense, which means we
> should be able to avoid any kind of synchronization for things like memory
> removals, as long as the userspace is aware of that.

A curious question. What about the backing storage of the affected GPA
is changed after adding back? Is recorded dirty info for previous backing
storage still making sense for the newer one?

Thanks
Kevin

>
> With that, when we fetch the dirty bits, we lookup the memslot dynamically,
> drop bits if the memslot does not exist on that address (e.g., permanent
> removals), and use whatever memslot is there for that guest physical
> address.
> Though we for sure still need to handle memory move, that the userspace
> needs
> to still take care of dirty bit flushing and sync for a memory move, however
> that's merely not happening so nothing to take care about either.
>
> Does this makes sense? Comments greatly welcomed..
>
> Thanks,
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2020-03/msg08361.html
>
> --
> Peter Xu

\
 
 \ /
  Last update: 2020-04-23 08:29    [W:0.472 / U:1.696 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site