On Thu, Mar 26, 2020 at 02:14:36PM +, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > On Wed, Mar 25, 2020 at 08:41:44PM +, Dr. David Alan Gilbert wrote:
> >
> > [...]
> >
> > > > +enum KVMReaperState {
> > > > +KVM_REAPER_NONE = 0,
> > > > +/* The reaper
* Peter Xu (pet...@redhat.com) wrote:
> On Wed, Mar 25, 2020 at 08:41:44PM +, Dr. David Alan Gilbert wrote:
>
> [...]
>
> > > +enum KVMReaperState {
> > > +KVM_REAPER_NONE = 0,
> > > +/* The reaper is sleeping */
> > > +KVM_REAPER_WAIT,
> > > +/* The reaper is reaping for dirt
On Wed, Mar 25, 2020 at 08:41:44PM +, Dr. David Alan Gilbert wrote:
[...]
> > +enum KVMReaperState {
> > +KVM_REAPER_NONE = 0,
> > +/* The reaper is sleeping */
> > +KVM_REAPER_WAIT,
> > +/* The reaper is reaping for dirty pages */
> > +KVM_REAPER_REAPING,
> > +};
>
> Tha
* Peter Xu (pet...@redhat.com) wrote:
> KVM dirty ring is a new interface to pass over dirty bits from kernel
> to the userspace. Instead of using a bitmap for each memory region,
> the dirty ring contains an array of dirtied GPAs to fetch. For each
> vcpu there will be one dirty ring that binds
KVM dirty ring is a new interface to pass over dirty bits from kernel
to the userspace. Instead of using a bitmap for each memory region,
the dirty ring contains an array of dirtied GPAs to fetch. For each
vcpu there will be one dirty ring that binds to it.
There're a few major changes comparing