On Mon, Apr 11, 2022 at 06:32:33PM +0300, Kirill A. Shutemov wrote:

On Thu, Apr 07, 2022 at 04:05:36PM +0000, Sean Christopherson wrote:

quoted

Hmm, shmem_writepage() already handles SHM_F_INACCESSIBLE by rejecting the swap, so
maybe it's just the page migration path that needs to be updated?

My early version prevented migration with -ENOTSUPP for
address_space_operations::migratepage().

What's wrong with that approach?

I previously thought migratepage will not be called since we already
marked the pages as UNMOVABLE, sounds not correct?

Thanks,
Chao

-- 
 Kirill A. Shutemov