Lines Matching full:migration

3  * Device Memory Migration functionality.
179 		 * any kind of migration. Side effect is that it "freezes" the  in migrate_vma_collect_pmd()
192 		 * migration as it is only best effort anyway.  in migrate_vma_collect_pmd()
194 		 * If we can lock the page it's safe to set up a migration entry  in migrate_vma_collect_pmd()
196 		 * single process setting up the migration entry now is an  in migrate_vma_collect_pmd()
226 			/* Setup special migration page table entry */  in migrate_vma_collect_pmd()
293  * @migrate: migrate struct containing all migration information
325  * folio_migrate_mapping(), except that here we allow migration of a
360  * Unmaps pages for migration. Returns number of source pfns marked as
440  * migrate_vma_unmap() - replace page mapping with special migration pte entry
441  * @migrate: migrate struct containing all migration information
444  * special migration pte entry and check if it has been pinned. Pinned pages are
458  * @args: contains the vma, start, and pfns arrays for the migration
479  * with MIGRATE_PFN_MIGRATE flag in src array unless this is a migration from
489  * properly set the destination entry like for regular migration.  Note that
491  * migration was successful for those entries after calling migrate_vma_pages(),
492  * just like for regular migration.
804  * @migrate: migrate struct containing all migration information
807  * struct page. This effectively finishes the migration from source page to the
817  * migrate_device_finalize() - complete page migration
822  * Completes migration of the page by removing special migration entries.
875  * @migrate: migrate struct containing all migration information
877  * This replaces the special migration pte entry with either a mapping to the
878  * new page if migration was successful for that page, or to the original page
939  * a reference on page which will be copied to the new page if migration is