On Sat, May 02, 2020 at 05:04:23PM -0400, Peter Xu wrote:
> Paolo,
>
> Do you have any opinion on this series? Or more generally comments on what's
> your preference to fix the known dirty sync issue with memslot removal would
> be
> welcomed too. For my own opinion, I prefer the approach with
On Wed, Apr 29, 2020 at 10:32:27AM -0400, Peter Xu wrote:
> On Wed, Apr 29, 2020 at 02:26:07PM +0100, Dr. David Alan Gilbert wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > This RFC series starts from the fact that we will sync dirty bitmap when
> > > removing a memslot for KVM. IIUC that w
On Wed, Apr 29, 2020 at 02:26:07PM +0100, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > This RFC series starts from the fact that we will sync dirty bitmap when
> > removing a memslot for KVM. IIUC that was majorly to maintain the dirty
> > bitmap
> > even across a sys
* Peter Xu (pet...@redhat.com) wrote:
> This RFC series starts from the fact that we will sync dirty bitmap when
> removing a memslot for KVM. IIUC that was majorly to maintain the dirty
> bitmap
> even across a system reboot.
>
> This series wants to move that sync from kvm memslot removal to s
This RFC series starts from the fact that we will sync dirty bitmap when
removing a memslot for KVM. IIUC that was majorly to maintain the dirty bitmap
even across a system reboot.
This series wants to move that sync from kvm memslot removal to system reset.
(I still don't know why the reset sys
