Lines Matching full:migration

3  * Device Memory Migration functionality.
172 		 * any kind of migration. Side effect is that it "freezes" the  in migrate_vma_collect_pmd()
185 		 * migration as it is only best effort anyway.  in migrate_vma_collect_pmd()
187 		 * If we can lock the page it's safe to set up a migration entry  in migrate_vma_collect_pmd()
189 		 * single process setting up the migration entry now is an  in migrate_vma_collect_pmd()
219 			/* Setup special migration page table entry */  in migrate_vma_collect_pmd()
287  * @migrate: migrate struct containing all migration information
319  * folio_migrate_mapping(), except that here we allow migration of a
354  * Unmaps pages for migration. Returns number of source pfns marked as
434  * migrate_vma_unmap() - replace page mapping with special migration pte entry
435  * @migrate: migrate struct containing all migration information
438  * special migration pte entry and check if it has been pinned. Pinned pages are
452  * @args: contains the vma, start, and pfns arrays for the migration
473  * with MIGRATE_PFN_MIGRATE flag in src array unless this is a migration from
483  * properly set the destination entry like for regular migration.  Note that
485  * migration was successful for those entries after calling migrate_vma_pages(),
486  * just like for regular migration.
789  * @migrate: migrate struct containing all migration information
792  * struct page. This effectively finishes the migration from source page to the
802  * migrate_device_finalize() - complete page migration
807  * Completes migration of the page by removing special migration entries.
860  * @migrate: migrate struct containing all migration information
862  * This replaces the special migration pte entry with either a mapping to the
863  * new page if migration was successful for that page, or to the original page
924  * a reference on page which will be copied to the new page if migration is