From: Zi Yan <ziy@nvidia.com>
To: Jordan Niethe <jniethe@nvidia.com>
Cc: linux-mm@kvack.org, balbirs@nvidia.com, matthew.brost@intel.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, david@redhat.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
Subject: Re: [PATCH v2 05/11] mm/page_vma_mapped: Add flags to page_vma_mapped_walk::pfn to track device private pages
Date: Tue, 20 Jan 2026 17:49:17 -0500 [thread overview]
Message-ID: <4784318E-D6AF-471B-A2E0-8B04EC0A238E@nvidia.com> (raw)
In-Reply-To: <e28edba2-889c-4590-ab2c-6ff377c36f05@nvidia.com>
On 20 Jan 2026, at 17:37, Jordan Niethe wrote:
> Hi,
>
> On 14/1/26 06:44, Zi Yan wrote:
>> On 7 Jan 2026, at 4:18, Jordan Niethe wrote:
>>
>>> A future change will remove device private pages from the physical
>>> address space. This will mean that device private pages no longer have
>>> normal PFN and must be handled separately.
>>>
>>> Prepare for this by modifying page_vma_mapped_walk::pfn to contain flags
>>> as well as a PFN. Introduce a PVMW_PFN_DEVICE_PRIVATE flag to indicate
>>> that a page_vma_mapped_walk::pfn contains a PFN for a device private
>>> page.
>>>
>>> Signed-off-by: Jordan Niethe <jniethe@nvidia.com>
>>> Signed-off-by: Alistair Popple <apopple@nvidia.com>
>>> ---
>>> v1:
>>> - Update for HMM huge page support
>>> v2:
>>> - Move adding device_private param to check_pmd() until final patch
>>> ---
>>> include/linux/rmap.h | 30 +++++++++++++++++++++++++++++-
>>> mm/page_vma_mapped.c | 13 +++++++------
>>> mm/rmap.c | 4 ++--
>>> mm/vmscan.c | 2 +-
>>> 4 files changed, 39 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/include/linux/rmap.h b/include/linux/rmap.h
>>> index daa92a58585d..57c63b6a8f65 100644
>>> --- a/include/linux/rmap.h
>>> +++ b/include/linux/rmap.h
>>> @@ -939,9 +939,37 @@ struct page_vma_mapped_walk {
>>> unsigned int flags;
>>> };
>>>
>>> +/* pfn is a device private offset */
>>> +#define PVMW_PFN_DEVICE_PRIVATE (1UL << 0)
>>> +#define PVMW_PFN_SHIFT 1
>>> +
>>> +static inline unsigned long page_vma_walk_pfn(unsigned long pfn)
>>> +{
>>> + return (pfn << PVMW_PFN_SHIFT);
>>> +}
>>> +
>>> +static inline unsigned long folio_page_vma_walk_pfn(const struct folio *folio)
>>> +{
>>> + if (folio_is_device_private(folio))
>>> + return page_vma_walk_pfn(folio_pfn(folio)) |
>>> + PVMW_PFN_DEVICE_PRIVATE;
>>> +
>>> + return page_vma_walk_pfn(folio_pfn(folio));
>>> +}
>>> +
>>> +static inline struct page *page_vma_walk_pfn_to_page(unsigned long pvmw_pfn)
>>> +{
>>> + return pfn_to_page(pvmw_pfn >> PVMW_PFN_SHIFT);
>>> +}
>>> +
>>> +static inline struct folio *page_vma_walk_pfn_to_folio(unsigned long pvmw_pfn)
>>> +{
>>> + return page_folio(page_vma_walk_pfn_to_page(pvmw_pfn));
>>> +}
>>> +
>>> #define DEFINE_FOLIO_VMA_WALK(name, _folio, _vma, _address, _flags) \
>>> struct page_vma_mapped_walk name = { \
>>> - .pfn = folio_pfn(_folio), \
>>> + .pfn = folio_page_vma_walk_pfn(_folio), \
>>> .nr_pages = folio_nr_pages(_folio), \
>>> .pgoff = folio_pgoff(_folio), \
>>> .vma = _vma, \
>>> diff --git a/mm/page_vma_mapped.c b/mm/page_vma_mapped.c
>>> index b38a1d00c971..96c525785d78 100644
>>> --- a/mm/page_vma_mapped.c
>>> +++ b/mm/page_vma_mapped.c
>>> @@ -129,9 +129,9 @@ static bool check_pte(struct page_vma_mapped_walk *pvmw, unsigned long pte_nr)
>>> pfn = softleaf_to_pfn(entry);
>>> }
>>>
>>> - if ((pfn + pte_nr - 1) < pvmw->pfn)
>>> + if ((pfn + pte_nr - 1) < (pvmw->pfn >> PVMW_PFN_SHIFT))
>>
>> Can you add a helper function for (pvmw->pfn >> PVMW_PFN_SHIFT)? It is impossible
>> to tell why pfn does not need >> PVMW_PFN_SHIFT.
>
> Sure, something like page_vma_walk_pfn_to_offset()?
>
Just page_vma_walk_pfn(pvmw)? Since the code is comparing with pfn.
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2026-01-20 22:49 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 9:18 [PATCH v2 00/11] Remove device private pages from physical address space Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 01/11] mm/migrate_device: Introduce migrate_pfn_from_page() helper Jordan Niethe
2026-01-08 20:03 ` Felix Kuehling
2026-01-08 23:49 ` Jordan Niethe
2026-01-09 21:03 ` Kuehling, Felix
2026-01-09 22:47 ` Balbir Singh
2026-01-07 9:18 ` [PATCH v2 02/11] drm/amdkfd: Use migrate pfns internally Jordan Niethe
2026-01-08 22:00 ` Felix Kuehling
2026-01-08 23:56 ` Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 03/11] mm/migrate_device: Make migrate_device_{pfns,range}() take mpfns Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 04/11] mm/migrate_device: Add migrate PFN flag to track device private pages Jordan Niethe
2026-01-08 20:01 ` Felix Kuehling
2026-01-08 23:41 ` Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 05/11] mm/page_vma_mapped: Add flags to page_vma_mapped_walk::pfn " Jordan Niethe
2026-01-13 19:44 ` Zi Yan
2026-01-20 22:37 ` Jordan Niethe
2026-01-20 22:49 ` Zi Yan [this message]
2026-01-20 22:52 ` Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 06/11] mm: Add helpers to create migration entries from struct pages Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 07/11] mm: Add a new swap type for migration entries of device private pages Jordan Niethe
2026-01-12 1:00 ` Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 08/11] mm: Add helpers to create device private entries from struct pages Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 09/11] mm/util: Add flag to track device private pages in page snapshots Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 10/11] mm/hmm: Add flag to track device private pages Jordan Niethe
2026-01-07 9:18 ` [PATCH v2 11/11] mm: Remove device private pages from the physical address space Jordan Niethe
2026-01-13 20:04 ` Zi Yan
2026-01-20 22:33 ` Jordan Niethe
2026-01-20 22:53 ` Zi Yan
2026-01-20 23:02 ` Jordan Niethe
2026-01-20 23:06 ` Zi Yan
2026-01-20 23:34 ` Jordan Niethe
2026-01-21 2:41 ` Zi Yan
2026-01-21 4:04 ` Jordan Niethe
2026-01-22 6:24 ` Jordan Niethe
2026-01-23 2:02 ` Alistair Popple
2026-01-23 3:06 ` Zi Yan
2026-01-23 3:09 ` Zi Yan
2026-01-23 5:38 ` Alistair Popple
2026-01-23 13:50 ` Jason Gunthorpe
2026-01-07 18:36 ` [PATCH v2 00/11] Remove device private pages from " Matthew Brost
2026-01-07 20:21 ` Zi Yan
2026-01-08 2:25 ` Jordan Niethe
2026-01-08 5:42 ` Jordan Niethe
2026-01-09 0:01 ` Jordan Niethe
2026-01-09 0:31 ` Matthew Brost
2026-01-09 1:27 ` Jordan Niethe
2026-01-09 6:22 ` Matthew Brost
2026-01-14 5:41 ` Jordan Niethe
2026-01-23 6:25 ` Jordan Niethe
2026-01-07 20:06 ` Andrew Morton
2026-01-07 20:54 ` Jason Gunthorpe
2026-01-07 21:02 ` Balbir Singh
2026-01-08 1:29 ` Alistair Popple
2026-01-08 1:08 ` John Hubbard
2026-01-08 1:49 ` Alistair Popple
2026-01-08 2:55 ` Jordan Niethe
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=4784318E-D6AF-471B-A2E0-8B04EC0A238E@nvidia.com \
--to=ziy@nvidia.com \
--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=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--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=matthew.brost@intel.com \
--cc=mpenttil@redhat.com \
--cc=rcampbell@nvidia.com \
--cc=simona@ffwll.ch \
--cc=willy@infradead.org \
/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