Re: [PATCH v3 1/1] mm/migrate: Add migrate_device_pfns

2024-10-24 Thread Andrew Morton
On Wed, 23 Oct 2024 16:39:43 -0700 Matthew Brost wrote: > Part of series [1]. Sending as individual patch ahead of that series as > this is a prerequisite for merging. That's news to me - singleton patches are perfectly OK? On Wed, 23 Oct 2024 16:39:44 -0700 Matthew Brost wrote: > Implement

Re: [PATCH v3 1/1] mm/migrate: Add migrate_device_pfns

2024-10-23 Thread Andrew Morton
On Thu, 24 Oct 2024 01:50:34 + Matthew Brost wrote: > > On Wed, 23 Oct 2024 16:39:44 -0700 Matthew Brost > > wrote: > > > > > Implement migrate_device_pfns to prepare an array of PFNs for migration. > > > Handles non-contiguous ranges of device pages that require migration. > > > > OK, t

Re: [PATCH v3 1/1] mm/migrate: Add migrate_device_pfns

2024-10-23 Thread Matthew Brost
On Wed, Oct 23, 2024 at 06:22:17PM -0700, Andrew Morton wrote: > On Wed, 23 Oct 2024 16:39:43 -0700 Matthew Brost > wrote: > > > Part of series [1]. Sending as individual patch ahead of that series as > > this is a prerequisite for merging. > > That's news to me - singleton patches are perfectl

[PATCH v3 1/1] mm/migrate: Add migrate_device_pfns

2024-10-23 Thread Matthew Brost
Implement migrate_device_pfns to prepare an array of PFNs for migration. Handles non-contiguous ranges of device pages that require migration. v2: - s/migrate_device_vma_range/migrate_device_prepopulated_range - Drop extra mmu invalidation (Vetter) v3: - s/migrate_device_prepopulated_range/migr