Re: [PATCH v4 3/6] support UFFD write fault processing in ram_save_iterate()

2020-11-30 Thread Andrey Gruzdev
On 30.11.2020 19:32, Peter Xu wrote: On Mon, Nov 30, 2020 at 12:14:03AM +0300, Andrey Gruzdev wrote: +#ifdef CONFIG_LINUX +/** + * ram_find_block_by_host_address: find RAM block containing host page + * + * Returns pointer to RAMBlock if found, NULL otherwise + * + * @rs: current RAM state + * @

Re: [PATCH v4 3/6] support UFFD write fault processing in ram_save_iterate()

2020-11-30 Thread Peter Xu
On Mon, Nov 30, 2020 at 12:14:03AM +0300, Andrey Gruzdev wrote: > > > +#ifdef CONFIG_LINUX > > > +/** > > > + * ram_find_block_by_host_address: find RAM block containing host page > > > + * > > > + * Returns pointer to RAMBlock if found, NULL otherwise > > > + * > > > + * @rs: current RAM state > >

Re: [PATCH v4 3/6] support UFFD write fault processing in ram_save_iterate()

2020-11-29 Thread Andrey Gruzdev
On 28.11.2020 00:49, Peter Xu wrote: On Thu, Nov 26, 2020 at 06:17:31PM +0300, Andrey Gruzdev wrote: In this particular implementation the same single migration thread is responsible for both normal linear dirty page migration and procesing UFFD page fault events. Processing write faults includ

Re: [PATCH v4 3/6] support UFFD write fault processing in ram_save_iterate()

2020-11-27 Thread Peter Xu
On Thu, Nov 26, 2020 at 06:17:31PM +0300, Andrey Gruzdev wrote: > In this particular implementation the same single migration > thread is responsible for both normal linear dirty page > migration and procesing UFFD page fault events. > > Processing write faults includes reading UFFD file descripto

[PATCH v4 3/6] support UFFD write fault processing in ram_save_iterate()

2020-11-26 Thread Andrey Gruzdev via
In this particular implementation the same single migration thread is responsible for both normal linear dirty page migration and procesing UFFD page fault events. Processing write faults includes reading UFFD file descriptor, finding respective RAM block and saving faulting page to the migration