From: Jason Gunthorpe <jgg@nvidia.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: airlied@gmail.com, akpm@linux-foundation.org, apopple@nvidia.com,
balbirs@nvidia.com, christian.koenig@amd.com, leonro@nvidia.com,
matthew.brost@intel.com, mm-commits@vger.kernel.org,
mpenttil@redhat.com, thomas.hellstrom@linux.intel.com,
ziy@nvidia.com
Subject: Re: [PATCH] mm/hmm: populate PFNs from PMD swap entry
Date: Mon, 8 Sep 2025 10:46:19 -0300 [thread overview]
Message-ID: <20250908134619.GH616306@nvidia.com> (raw)
In-Reply-To: <20250908091052.612303-1-francois.dugast@intel.com>
On Mon, Sep 08, 2025 at 11:10:52AM +0200, Francois Dugast wrote:
> Once support for THP migration of zone device pages is enabled, device
> private swap entries will be found during the walk not only for PTEs but
> also for PMDs.
>
> Therefore, it is necessary to extend to PMDs the special handling which is
> already in place for PTEs when device private pages are owned by the
> caller: instead of faulting or skipping the range, the correct behavior is
> to use the swap entry to populate HMM PFNs.
>
> This change is a prerequisite to make use of device-private THP in drivers
> using drivers/gpu/drm/drm_pagemap, such as xe.
>
> Even though subsequent PFNs can be inferred when handling large order
> PFNs, the PFN list is still fully populated because this is currently
> expected by HMM users. In case this changes in the future, that is all HMM
> users support a sparsely populated PFN list, the for() loop can be made to
> skip remaining PFNs for the current order. A quick test shows the loop
> takes about 10 ns, roughly 20 times faster than without this optimization.
>
> Cc: Jason Gunthorpe <jgg@nvidia.com>
> Cc: Leon Romanovsky <leonro@nvidia.com>
> Cc: Zi Yan <ziy@nvidia.com>
> Cc: Alistair Popple <apopple@nvidia.com>
> Cc: Balbir Singh <balbirs@nvidia.com>
> Cc: David Airlie <airlied@gmail.com>
> Cc: Christian König <christian.koenig@amd.com>
> Cc: Mika Penttilä <mpenttil@redhat.com>
> Cc: Thomas Hellstrom <thomas.hellstrom@linux.intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
> ---
> mm/hmm.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 65 insertions(+), 5 deletions(-)
Please put version numbers on your patches and include a change log.
Jason
next prev parent reply other threads:[~2025-09-08 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 3:56 + mm-hmm-populate-pfns-from-pmd-swap-entry.patch added to mm-new branch Andrew Morton
2025-09-02 11:17 ` [PATCH] mm/hmm: populate PFNs from PMD swap entry Francois Dugast
2025-09-02 11:30 ` Balbir Singh
2025-09-02 12:53 ` Francois Dugast
2025-09-02 13:07 ` Francois Dugast
2025-09-03 5:47 ` Matthew Brost
2025-09-04 13:25 ` Francois Dugast
2025-09-08 9:10 ` Francois Dugast
2025-09-08 13:46 ` Jason Gunthorpe [this message]
2025-09-09 1:50 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2025-08-29 8:05 [PATCH] mm/hmm: Populate " Francois Dugast
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=20250908134619.GH616306@nvidia.com \
--to=jgg@nvidia.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=francois.dugast@intel.com \
--cc=leonro@nvidia.com \
--cc=matthew.brost@intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=mpenttil@redhat.com \
--cc=thomas.hellstrom@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.