mirror of
https://github.com/torvalds/linux.git
synced 2026-11-07 06:17:02 +01:00
mm/migrate_device: fix function name in kernel-doc
The kernel-doc for migrate_device_range() says that migrate_vma_setup() is
similar to itself. Refer to migrate_device_range() as the subject of the
comparison, making the distinction between virtual-address-based and
device-PFN-based migration clear.
Link: https://lore.kernel.org/13768B0F4A5FC1F5+20260902031229.1821112-1-zhaozhengzhuo@uniontech.com
Fixes: e778406b40 ("mm/migrate_device.c: add migrate_device_range()")
Signed-off-by: zhaozhengzhuo <zhaozhengzhuo@uniontech.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Zi Yan <ziy@nvidia.com>
Cc: Alistair Popple <apopple@nvidia.com>
Cc: David Hildenbrand <david@kernel.org>
Cc: Byungchul Park <byungchul@sk.com>
Cc: Gregory Price <gourry@gourry.net>
Cc: "Huang, Ying" <ying.huang@linux.alibaba.com>
Cc: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Rakie Kim <rakie.kim@sk.com>
This commit is contained in:
parent
6f64100221
commit
ae62466cda
|
|
@ -1398,9 +1398,9 @@ static unsigned long migrate_device_pfn_lock(unsigned long pfn)
|
|||
* @start: starting pfn in the range to migrate.
|
||||
* @npages: number of pages to migrate.
|
||||
*
|
||||
* migrate_vma_setup() is similar in concept to migrate_vma_setup() except that
|
||||
* instead of looking up pages based on virtual address mappings a range of
|
||||
* device pfns that should be migrated to system memory is used instead.
|
||||
* migrate_device_range() is similar in concept to migrate_vma_setup(), except
|
||||
* that instead of looking up pages based on virtual address mappings, a range
|
||||
* of device pfns that should be migrated to system memory is used.
|
||||
*
|
||||
* This is useful when a driver needs to free device memory but doesn't know the
|
||||
* virtual mappings of every page that may be in device memory. For example this
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user