Re: [RFC PATCH 9/9] kvm_main.c: handle atomic memslot update

[David Hildenbrand]

On 09.09.22 12:45, Emanuele Giuseppe Esposito wrote:
> When kvm_vm_ioctl_set_memory_region_list() is invoked, we need
> to make sure that all memslots are updated in the inactive list
> and then swap (preferreably only once) the lists, so that all
> changes are visible immediately.
>
> The only issue is that DELETE and MOVE need to perform 2 swaps:
> firstly replace old memslot with invalid, and then remove invalid.

I'm curious, how would a resize (grow/shrink) or a split be handled?

--
Thanks,

David / dhildenb