From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Jordan Niethe <jniethe@nvidia.com>, linux-mm@kvack.org
Cc: balbirs@nvidia.com, matthew.brost@intel.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, ziy@nvidia.com,
apopple@nvidia.com, lorenzo.stoakes@oracle.com, lyude@redhat.com,
dakr@kernel.org, airlied@gmail.com, simona@ffwll.ch,
rcampbell@nvidia.com, mpenttil@redhat.com, jgg@nvidia.com,
willy@infradead.org, linuxppc-dev@lists.ozlabs.org,
intel-xe@lists.freedesktop.org, jgg@ziepe.ca,
Felix.Kuehling@amd.com, jhubbard@nvidia.com, maddy@linux.ibm.com,
mpe@ellerman.id.au, ying.huang@linux.alibaba.com
Subject: Re: [PATCH v6 01/13] mm/migrate_device: Introduce migrate_pfn_from_page() helper
Date: Tue, 3 Mar 2026 17:32:43 +0100 [thread overview]
Message-ID: <c5584cf8-1389-4df4-9fb7-19d9ee26ab9c@kernel.org> (raw)
In-Reply-To: <faaa84fd-095e-440b-9922-b4037a67416d@nvidia.com>
On 3/3/26 06:52, Jordan Niethe wrote:
> Hi
>
> On 2/3/26 20:22, David Hildenbrand (Arm) wrote:
>> On 3/2/26 00:38, Jordan Niethe wrote:
>>> Hi,
>>>
>>
>> I'll go through he remainder of the patchset this week.
>
> Much appreciated.
>
>>
>> While skimming over patch #2, I was wondering whether
>> "page_to_migration_pfn()" would better fit "migration_pfn_to_page".
>
> I guess you were thinking about migration_pfn_/from/_page() rather than
> "migration_pfn_to_page()"? Renaming it to page_to_migration_pfn() would
> be fine.
Yes. :)
page_to_migration_pfn() and migration_pfn_to_page()
But really, we should only be dealing with folio migration longterm ...
>
>>
>> ... and I was wondering why that code deals with pages instead of folios.
>
>>
>> E.g.,
>>
>> page = folio_page(folio, 0);
>> mpfn[i] = migrate_pfn_from_page(page);
>>
>> Should just be
>>
>> mpfn[i] = folio_to_migration_pfn(folio);
>>
>> Right?
>
> This patch is quite limited, essentially just converts usages of
> migrate_pfn(page_to_pfn()) to migration_pfn_from_page(). However, I
> agree, there could be scope for moving some of those usages to folios.
>
> Was that example from drm_pagemap_migrate_populate_ram_pfn()? There
> 'page' goes on to be used elsewhere in the function so we'd need some
> further refactoring to fully benefit.
>
> I see migrate_vma_collect_huge_pmd() as a candidate for a
> folio_to_migration_pfn() function too.
All that code should be converted to folios (unless I am missing
something important). We only support migration of folios, and all
ZONE_DEVICE pages correspond to folios.
E.g., in migrate_vma_setup() we're implicitly converting from page to
folio multiple times, which is rather wasteful.
Now, I don't think the conversion is your responsibility :)
But you'd provide the folio helpers and use them where we can already.
I'm fine with leaving the code the still operates purely on page to be
converted later.
--
Cheers,
David
next prev parent reply other threads:[~2026-03-03 16:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 11:36 [PATCH v6 00/13] Remove device private pages from physical address space Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 01/13] mm/migrate_device: Introduce migrate_pfn_from_page() helper Jordan Niethe
2026-02-27 21:11 ` David Hildenbrand (Arm)
2026-03-01 23:38 ` Jordan Niethe
2026-03-02 9:22 ` David Hildenbrand (Arm)
2026-03-03 5:52 ` Jordan Niethe
2026-03-03 16:32 ` David Hildenbrand (Arm) [this message]
2026-02-02 11:36 ` [PATCH v6 02/13] drm/amdkfd: Use migrate pfns internally Jordan Niethe
2026-03-03 16:40 ` David Hildenbrand (Arm)
2026-02-02 11:36 ` [PATCH v6 03/13] mm/migrate_device: Make migrate_device_{pfns,range}() take mpfns Jordan Niethe
2026-03-03 16:52 ` David Hildenbrand (Arm)
2026-02-02 11:36 ` [PATCH v6 04/13] mm/migrate_device: Add migrate PFN flag to track device private pages Jordan Niethe
2026-03-03 16:58 ` David Hildenbrand (Arm)
2026-02-02 11:36 ` [PATCH v6 05/13] mm/page_vma_mapped: Add flag to page_vma_mapped_walk::flags " Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 06/13] mm: Add helpers to create migration entries from struct pages Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 07/13] mm: Add a new swap type for migration entries of device private pages Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 08/13] mm: Add softleaf support for device private migration entries Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 09/13] mm: Begin creating " Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 10/13] mm: Add helpers to create device private entries from struct pages Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 11/13] mm/util: Add flag to track device private pages in page snapshots Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 12/13] mm/hmm: Add flag to track device private pages Jordan Niethe
2026-02-02 11:36 ` [PATCH v6 13/13] mm: Remove device private pages from the physical address space Jordan Niethe
2026-02-06 13:08 ` [PATCH v6 00/13] Remove device private pages from " David Hildenbrand (Arm)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c5584cf8-1389-4df4-9fb7-19d9ee26ab9c@kernel.org \
--to=david@kernel.org \
--cc=Felix.Kuehling@amd.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=jniethe@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lyude@redhat.com \
--cc=maddy@linux.ibm.com \
--cc=matthew.brost@intel.com \
--cc=mpe@ellerman.id.au \
--cc=mpenttil@redhat.com \
--cc=rcampbell@nvidia.com \
--cc=simona@ffwll.ch \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox