linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbirs@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	dri-devel@lists.freedesktop.org,
	"David Hildenbrand" <david@redhat.com>, "Zi Yan" <ziy@nvidia.com>,
	"Joshua Hahn" <joshua.hahnjy@gmail.com>,
	"Rakie Kim" <rakie.kim@sk.com>,
	"Byungchul Park" <byungchul@sk.com>,
	"Gregory Price" <gourry@gourry.net>,
	"Ying Huang" <ying.huang@linux.alibaba.com>,
	"Alistair Popple" <apopple@nvidia.com>,
	"Oscar Salvador" <osalvador@suse.de>,
	"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
	"Baolin Wang" <baolin.wang@linux.alibaba.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Nico Pache" <npache@redhat.com>,
	"Ryan Roberts" <ryan.roberts@arm.com>,
	"Dev Jain" <dev.jain@arm.com>, "Barry Song" <baohua@kernel.org>,
	"Lyude Paul" <lyude@redhat.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Ralph Campbell" <rcampbell@nvidia.com>,
	"Mika Penttilä" <mpenttil@redhat.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Francois Dugast" <francois.dugast@intel.com>
Subject: Re: [PATCH] fixup: mm/rmap: extend rmap and migration support device-private entries
Date: Sat, 15 Nov 2025 13:32:00 +1100	[thread overview]
Message-ID: <e1f3074b-c4d4-47e3-9303-18ba254e3662@nvidia.com> (raw)
In-Reply-To: <20251114165146.5c51eeeee200bd37b378bd45@linux-foundation.org>

On 11/15/25 11:51, Andrew Morton wrote:
> On Sat, 15 Nov 2025 11:28:35 +1100 Balbir Singh <balbirs@nvidia.com> wrote:
> 
>> Follow the pattern used in remove_migration_pte() in
>> remove_migration_pmd(). Process the migration entries and if the entry
>> type is device private, override the pmde with a device private entry
>> and set the soft dirty and uffd_wp bits with the pmd_swp_mksoft_dirty
>> and pmd_swp_mkuffd_wp
>>
>> ...
>>
>> This fixup should be squashed into the patch "mm/rmap: extend rmap and
>> migration support" of mm/mm-unstable
>>
> 
> OK.  After fixing up
> mm-replace-pmd_to_swp_entry-with-softleaf_from_pmd.patch, mm.git's
> mm/huge_memory.c has the below.  Please double-check.
> 
> 
> void remove_migration_pmd(struct page_vma_mapped_walk *pvmw, struct page *new)
> {
> 	struct folio *folio = page_folio(new);
> 	struct vm_area_struct *vma = pvmw->vma;
> 	struct mm_struct *mm = vma->vm_mm;
> 	unsigned long address = pvmw->address;
> 	unsigned long haddr = address & HPAGE_PMD_MASK;
> 	pmd_t pmde;
> 	softleaf_t entry;
> 
> 	if (!(pvmw->pmd && !pvmw->pte))
> 		return;
> 
> 	entry = softleaf_from_pmd(*pvmw->pmd);
> 	folio_get(folio);
> 	pmde = folio_mk_pmd(folio, READ_ONCE(vma->vm_page_prot));
> 
> 	if (pmd_swp_soft_dirty(*pvmw->pmd))
> 		pmde = pmd_mksoft_dirty(pmde);
> 	if (softleaf_is_migration_write(entry))
> 		pmde = pmd_mkwrite(pmde, vma);
> 	if (pmd_swp_uffd_wp(*pvmw->pmd))
> 		pmde = pmd_mkuffd_wp(pmde);
> 	if (!softleaf_is_migration_young(entry))
> 		pmde = pmd_mkold(pmde);
> 	/* NOTE: this may contain setting soft-dirty on some archs */
> 	if (folio_test_dirty(folio) && softleaf_is_migration_dirty(entry))
> 		pmde = pmd_mkdirty(pmde);
> 
> 	if (folio_is_device_private(folio)) {
> 		swp_entry_t entry;
> 
> 		if (pmd_write(pmde))
> 			entry = make_writable_device_private_entry(
> 							page_to_pfn(new));
> 		else
> 			entry = make_readable_device_private_entry(
> 							page_to_pfn(new));
> 		pmde = swp_entry_to_pmd(entry);
> 
> 		if (pmd_swp_soft_dirty(*pvmw->pmd))
> 			pmde = pmd_swp_mksoft_dirty(pmde);
> 		if (pmd_swp_uffd_wp(*pvmw->pmd))
> 			pmde = pmd_swp_mkuffd_wp(pmde);
> 	}
> 
> 	if (folio_test_anon(folio)) {
> 		rmap_t rmap_flags = RMAP_NONE;
> 
> 		if (!softleaf_is_migration_read(entry))
> 			rmap_flags |= RMAP_EXCLUSIVE;
> 
> 		folio_add_anon_rmap_pmd(folio, new, vma, haddr, rmap_flags);
> 	} else {
> 		folio_add_file_rmap_pmd(folio, new, vma);
> 	}
> 	VM_BUG_ON(pmd_write(pmde) && folio_test_anon(folio) && !PageAnonExclusive(new));
> 	set_pmd_at(mm, haddr, pvmw->pmd, pmde);
> 
> 	/* No need to invalidate - it was non-present before */
> 	update_mmu_cache_pmd(vma, address, pvmw->pmd);
> 	trace_remove_migration_pmd(address, pmd_val(pmde));
> }


Thanks, Andrew! Looks good!

Balbir


  reply	other threads:[~2025-11-15  2:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-15  0:28 Balbir Singh
2025-11-15  0:51 ` Andrew Morton
2025-11-15  2:32   ` Balbir Singh [this message]
2025-11-17 12:58 ` David Hildenbrand (Red Hat)
2025-11-17 22:39   ` Balbir Singh

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=e1f3074b-c4d4-47e3-9303-18ba254e3662@nvidia.com \
    --to=balbirs@nvidia.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=byungchul@sk.com \
    --cc=dakr@kernel.org \
    --cc=david@redhat.com \
    --cc=dev.jain@arm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=francois.dugast@intel.com \
    --cc=gourry@gourry.net \
    --cc=joshua.hahnjy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=lyude@redhat.com \
    --cc=matthew.brost@intel.com \
    --cc=mpenttil@redhat.com \
    --cc=npache@redhat.com \
    --cc=osalvador@suse.de \
    --cc=rakie.kim@sk.com \
    --cc=rcampbell@nvidia.com \
    --cc=ryan.roberts@arm.com \
    --cc=simona@ffwll.ch \
    --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