Re: [PULL 09/12] kvm: clear dirty bitmaps from all overlapping memslots

2019-10-02 Thread Paolo Bonzini
On 02/10/19 18:13, Christian Borntraeger wrote: > Does > > diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c > index aabe097c410f..e2605da22e7e 100644 > --- a/accel/kvm/kvm-all.c > +++ b/accel/kvm/kvm-all.c > @@ -712,7 +712,7 @@ static int kvm_physical_log_clear(KVMMemoryListener *kml, >

Re: [PULL 09/12] kvm: clear dirty bitmaps from all overlapping memslots

2019-10-02 Thread Christian Borntraeger
On 02.10.19 18:01, Kevin Wolf wrote: > Am 30.09.2019 um 15:19 hat Christian Borntraeger geschrieben: >> From: Paolo Bonzini >> >> Currently MemoryRegionSection has 1:1 mapping to KVMSlot. >> However next patch will allow splitting MemoryRegionSection into >> several KVMSlot-s, make sure that

Re: [PULL 09/12] kvm: clear dirty bitmaps from all overlapping memslots

2019-10-02 Thread Kevin Wolf
Am 30.09.2019 um 15:19 hat Christian Borntraeger geschrieben: > From: Paolo Bonzini > > Currently MemoryRegionSection has 1:1 mapping to KVMSlot. > However next patch will allow splitting MemoryRegionSection into > several KVMSlot-s, make sure that kvm_physical_log_slot_clear() > is able to

[PULL 09/12] kvm: clear dirty bitmaps from all overlapping memslots

2019-09-30 Thread Christian Borntraeger
From: Paolo Bonzini Currently MemoryRegionSection has 1:1 mapping to KVMSlot. However next patch will allow splitting MemoryRegionSection into several KVMSlot-s, make sure that kvm_physical_log_slot_clear() is able to handle such 1:N mapping. Signed-off-by: Paolo Bonzini Signed-off-by: Igor