Lines Matching full:migration

3  * Device Memory Migration functionality.
186 		 * any kind of migration. Side effect is that it "freezes" the  in migrate_vma_collect_pmd()
200 		 * migration as it is only best effort anyway.  in migrate_vma_collect_pmd()
202 		 * If we can lock the folio it's safe to set up a migration entry  in migrate_vma_collect_pmd()
204 		 * single process setting up the migration entry now is an  in migrate_vma_collect_pmd()
236 			/* Setup special migration page table entry */  in migrate_vma_collect_pmd()
304  * @migrate: migrate struct containing all migration information
336  * folio_migrate_mapping(), except that here we allow migration of a
373  * Unmaps pages for migration. Returns number of source pfns marked as
456  * migrate_vma_unmap() - replace page mapping with special migration pte entry
457  * @migrate: migrate struct containing all migration information
460  * special migration pte entry and check if it has been pinned. Pinned pages are
474  * @args: contains the vma, start, and pfns arrays for the migration
495  * with MIGRATE_PFN_MIGRATE flag in src array unless this is a migration from
505  * properly set the destination entry like for regular migration.  Note that
507  * migration was successful for those entries after calling migrate_vma_pages(),
508  * just like for regular migration.
809  * @migrate: migrate struct containing all migration information
812  * struct page. This effectively finishes the migration from source page to the
874  * migrate_device_finalize() - complete page migration
879  * Completes migration of the page by removing special migration entries.
892  * @migrate: migrate struct containing all migration information
894  * This replaces the special migration pte entry with either a mapping to the
895  * new page if migration was successful for that page, or to the original page
980  * a reference on folio which will be copied to the new folio if migration is