3  * Memory Migration functionality - linux/mm/migrate.c
7  * Page migration was first developed in the context of the memory hotplug
8  * project. The main authors of the migration code are:
95 	 * compaction threads can race against page migration functions  in isolate_movable_page()
99 	 * being (wrongly) re-isolated while it is under migration,  in isolate_movable_page()
141  * from where they were once taken off for compaction/migration.
181  * Restore a potential migration pte to a working pte entry
202 		/* PMD-mapped THP migration entry */  in remove_migration_pte()
282  * Get rid of all migration entries and replace them by
299  * Something used the pte of a page under migration. We need to
300  * get to the page and wait until migration is finished.
352 		 * If migration entry existed, safe to release vma lock  in migration_entry_wait_huge()
571 	 * migration entries. We can still have PG_anon_exclusive set on an  in folio_migrate_flags()
649  *                    Migration functions
672  * migrate_folio() - Simple folio migration.
802  * buffer_migrate_folio() - Migration function for folios with buffers.
824  * buffer_migrate_folio_norefs() - Migration function for folios with buffers.
890 	 * migration. Writeout may mean we lose the lock and the  in writeout()
892 	 * At this point we know that the migration attempt cannot  in writeout()
907  * Default handling if a filesystem does not provide a migration function.
913 		/* Only writeback folios in full synchronous migration */  in fallback_migrate_folio()
965 			 * for page migration.  in move_to_new_folio()
976 		 * isolation step. In that case, we shouldn't try migration.  in move_to_new_folio()
1022  * To record some information during migration, we use some unused
1081 /* Cleanup src folio upon migration success */
1164 		 * Only in the case of a full synchronous migration is it  in migrate_folio_unmap()
1184 	 * of migration. File cache pages are no problem because of page_lock()  in migrate_folio_unmap()
1185 	 * File Caches may use write_page() or lock_page() in migration, then,  in migrate_folio_unmap()
1232 		/* Establish migration ptes */  in migrate_folio_unmap()
1301 	 * If migration is successful, decrease refcount of dst,  in migrate_folio_move()
1337  * Counterpart of unmap_and_move_page() for hugepage migration.
1340  * because there is no race between I/O and migration for hugepage.
1348  * hugepage migration fails without data corruption.
1350  * There is also no race when direct I/O is issued on the page under migration,
1351  * because then pte is replaced with migration swap entry and direct I/O code
1352  * will wait in the page fault for migration to complete.
1456 	 * If migration was not successful and there's a freeing callback, use  in unmap_and_move_huge_page()
1536 			 * of hugepage migration like soft offline and memory  in migrate_hugetlbs()
1538 			 * the hugepage is pmd-based or not before kicking migration.  in migrate_hugetlbs()
1577 				 * removed from migration folio list and not  in migrate_hugetlbs()
1601  * We only batch migration if mode == MIGRATE_ASYNC to avoid to wait a
1639 			 * Large folio migration might be unsupported or  in migrate_pages_batch()
1728 				 * removed from migration folio list and not  in migrate_pages_batch()
1861  *		   supplied as the target for the page migration
1865  *			as the target of the folio migration.
1866  * @put_new_folio:	The function used to free target folios if migration
1869  * @mode:		The migration mode that specifies the constraints for
1870  *			folio migration, if any.
1871  * @reason:		The reason for folio migration.
1954 	 * Put the permanent failure folio back to migration list, they  in migrate_pages()
2005 		 * clear __GFP_RECLAIM to make the migration callback  in alloc_migration_target()
2222 			/* The page is successfully queued for migration */  in do_pages_move()
2452  * Returns true if this is a safe migration target node for misplaced NUMA
2528 	 * disappearing underneath us during migration.  in numamigrate_isolate_page()