From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 479D6C8CE for ; Thu, 25 Jun 2026 02:39:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782355189; cv=none; b=TvkBykyPrSIBZ7WbcHeW3hmsAG2u00BbLvDJulQlkmXbR/xn1kmJJupW95+x3g2Cmg5xlv4vWsr7mnpG3b1Hbvemg5+OFZ5s+D9uh74Lbu70fW1zajRr6tgjawA7i9Sp1gbTyfrtSErVV00Js62tuYAbrgLe7bEb16w/pckK0vw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782355189; c=relaxed/simple; bh=7I7N3VD6svtTH86eu3jafV+kNPMl+M2bVbr0dvYRtuM=; h=Date:To:From:Subject:Message-Id; b=oCwiMeOHpcKnVxf4ys5OSiBIIl16/V2HryHY/YDJt4LnuS4VnGtQ2tl9ck+KFt2HQICvVLf+UJmXtgQnh7+HTjLR73PxuheVF5rgrJBjzhN2nVE638y/IojSD+erRzDaVyQLIp4dLHx51htg2+geVFeMULbEBcq4ArDgFzyZUJ0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=b5SebpGQ; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="b5SebpGQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D27491F000E9; Thu, 25 Jun 2026 02:39:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=korg; t=1782355187; bh=MkC/q3TvgDhVimAZBp4zfB+rxLOsDcstxTpBGZKimV4=; h=Date:To:From:Subject; b=b5SebpGQqnS1Do325wiKTofzbDXnoQwhqDnGCIZb1WUAPYyTgDQUP4OGnVH8HxVbB Xd2JHVXAUbNo3cM3B3R8yJ2NdB2JGANc0Mv8EokbH5OWtCFGv0di4nkK5ZArmzYVyz N565w65GLrdT5g15q/XTC+E8x2ZMfA0hIX+Jodhg= Date: Wed, 24 Jun 2026 19:39:47 -0700 To: mm-commits@vger.kernel.org,ziy@nvidia.com,ying.huang@linux.alibaba.com,vbabka@kernel.org,surenb@google.com,rakie.kim@sk.com,pfalcato@suse.de,matthew.brost@intel.com,ljs@kernel.org,liam@infradead.org,joshua.hahnjy@gmail.com,gourry@gourry.net,david@kernel.org,byungchul@sk.com,apopple@nvidia.com,wangkefeng.wang@huawei.com,akpm@linux-foundation.org From: Andrew Morton Subject: + mm-migrate_device-use-walk_page_range_vma-in-migrate_vma_collect.patch added to mm-new branch Message-Id: <20260625023947.D27491F000E9@smtp.kernel.org> Precedence: bulk X-Mailing-List: mm-commits@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: The patch titled Subject: mm: migrate_device: use walk_page_range_vma() in migrate_vma_collect() has been added to the -mm mm-new branch. Its filename is mm-migrate_device-use-walk_page_range_vma-in-migrate_vma_collect.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-migrate_device-use-walk_page_range_vma-in-migrate_vma_collect.patch This patch will later appear in the mm-new branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm Note, mm-new is a provisional staging ground for work-in-progress patches, and acceptance into mm-new is a notification for others take notice and to finish up reviews. Please do not hesitate to respond to review feedback and post updated versions to replace or incrementally fixup patches in mm-new. The mm-new branch of mm.git is not included in linux-next If a few days of testing in mm-new is successful, the patch will me moved into mm.git's mm-unstable branch, which is included in linux-next Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next via various branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm and is updated there most days ------------------------------------------------------ From: Kefeng Wang Subject: mm: migrate_device: use walk_page_range_vma() in migrate_vma_collect() Date: Thu, 18 Jun 2026 17:28:45 +0800 migrate_vma_collect() uses walk_page_range() to walk the page table. Fortunately, migrate_vma_setup() already validates that the entire range falls within a single VMA. Since there is no .test_walk in migrate_vma_walk_ops and VM_PFNMAP was filtered by migrate_vma_setup(), it's safe to replace walk_page_range() with walk_page_range_vma() to eliminate an unnecessary find_vma() lookup. Link: https://lore.kernel.org/20260618092845.3905740-5-wangkefeng.wang@huawei.com Signed-off-by: Kefeng Wang Reviewed-by: Zi Yan Acked-by: David Hildenbrand (Arm) Acked-by: Pedro Falcato Cc: Alistair Popple Cc: Byungchul Park Cc: Gregory Price Cc: Joshua Hahn Cc: Liam R. Howlett Cc: Lorenzo Stoakes Cc: Matthew Brost Cc: Rakie Kim Cc: Suren Baghdasaryan Cc: Vlastimil Babka Cc: Ying Huang Signed-off-by: Andrew Morton --- mm/migrate_device.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/mm/migrate_device.c~mm-migrate_device-use-walk_page_range_vma-in-migrate_vma_collect +++ a/mm/migrate_device.c @@ -513,7 +513,7 @@ static void migrate_vma_collect(struct m migrate->pgmap_owner); mmu_notifier_invalidate_range_start(&range); - walk_page_range(migrate->vma->vm_mm, migrate->start, migrate->end, + walk_page_range_vma(migrate->vma, migrate->start, migrate->end, &migrate_vma_walk_ops, migrate); mmu_notifier_invalidate_range_end(&range); _ Patches currently in -mm which might be from wangkefeng.wang@huawei.com are mm-remove-pagetranscompound.patch mm-mincore-use-walk_page_range_vma-in-do_mincore.patch mm-mprotect-use-walk_page_range_vma-in-mprotect_fixup.patch mm-mlock-use-walk_page_range_vma-in-mlock_vma_pages_range.patch mm-migrate_device-use-walk_page_range_vma-in-migrate_vma_collect.patch