nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Alistair Popple <apopple@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	 gerald.schaefer@linux.ibm.com, dan.j.williams@intel.com,
	jgg@ziepe.ca, willy@infradead.org,  linux-kernel@vger.kernel.org,
	nvdimm@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	 linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
	jhubbard@nvidia.com, hch@lst.de,  zhang.lyra@gmail.com,
	debug@rivosinc.com, bjorn@kernel.org, balbirs@nvidia.com,
	 lorenzo.stoakes@oracle.com,
	linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
	 linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
	linux-cxl@vger.kernel.org,  dri-devel@lists.freedesktop.org,
	John@groves.net, m.szyprowski@samsung.com
Subject: Re: [PATCH v2 06/14] mm/huge_memory: Remove pXd_devmap usage from insert_pXd_pfn()
Date: Thu, 19 Jun 2025 18:52:19 +1000	[thread overview]
Message-ID: <esagpnu4oqjpfhvvzfhg6ux5pbikalurex7aw3lelwto4qqzft@vsgljrouwuv7> (raw)
In-Reply-To: <6bb233ef-5e56-4546-b571-6a5f052d8b45@redhat.com>

On Tue, Jun 17, 2025 at 11:49:20AM +0200, David Hildenbrand wrote:
> On 16.06.25 13:58, Alistair Popple wrote:
> > Nothing uses PFN_DEV anymore so no need to create devmap pXd's when
> > mapping a PFN. Instead special mappings will be created which ensures
> > vm_normal_page_pXd() will not return pages which don't have an
> > associated page. This could change behaviour slightly on architectures
> > where pXd_devmap() does not imply pXd_special() as the normal page
> > checks would have fallen through to checking VM_PFNMAP/MIXEDMAP instead,
> > which in theory at least could have returned a page.
> > 
> > However vm_normal_page_pXd() should never have been returning pages for
> > pXd_devmap() entries anyway, so anything relying on that would have been
> > a bug.
> > 
> > Signed-off-by: Alistair Popple <apopple@nvidia.com>
> > 
> > ---
> > 
> > Changes since v1:
> > 
> >   - New for v2
> > ---
> >   mm/huge_memory.c | 12 ++----------
> >   1 file changed, 2 insertions(+), 10 deletions(-)
> > 
> > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > index b096240..6514e25 100644
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
> > @@ -1415,11 +1415,7 @@ static int insert_pmd(struct vm_area_struct *vma, unsigned long addr,
> >   		add_mm_counter(mm, mm_counter_file(fop.folio), HPAGE_PMD_NR);
> >   	} else {
> >   		entry = pmd_mkhuge(pfn_t_pmd(fop.pfn, prot));
> > -
> > -		if (pfn_t_devmap(fop.pfn))
> > -			entry = pmd_mkdevmap(entry);
> > -		else
> > -			entry = pmd_mkspecial(entry);
> > +		entry = pmd_mkspecial(entry);
> >   	}
> >   	if (write) {
> >   		entry = pmd_mkyoung(pmd_mkdirty(entry));
> > @@ -1565,11 +1561,7 @@ static void insert_pud(struct vm_area_struct *vma, unsigned long addr,
> >   		add_mm_counter(mm, mm_counter_file(fop.folio), HPAGE_PUD_NR);
> >   	} else {
> >   		entry = pud_mkhuge(pfn_t_pud(fop.pfn, prot));
> > -
> > -		if (pfn_t_devmap(fop.pfn))
> > -			entry = pud_mkdevmap(entry);
> > -		else
> > -			entry = pud_mkspecial(entry);
> > +		entry = pud_mkspecial(entry);
> >   	}
> >   	if (write) {
> >   		entry = pud_mkyoung(pud_mkdirty(entry));
> 
> 
> Why not squash this patch into #3, and remove the pmd_special() check from
> vm_normal_page_pmd() in the same go? Seems wrong to handle the PMD/PUD case
> separately.

Yeah, that was mostly because "someone" (and thankyou btw, it was somewhat my
mess) changed all this while I was working on it :-) I wanted to make the rebase
fixups obvious but will squash them for v3.

> But now I am confused why some pte_devmap() checks are removed in patch #3,
> while others are removed in #7.
> 
> Why not split it up into (a) stop setting p*_devmap() and (b) remove
> p*_devmap().
> 
> Logically makes more sense to me ... :)

Heh. You're right. For various reasons this patch series has gone through a
couple of reorderings, mainly to get rid of unused stuff early in the series but
that didn't work out due to that RISC-V bug. I needed a break from silly rebase
build errors so this was a good checkpoint.

But I've reworked things for v3 to get the ordering a bit more sensible.

> -- 
> Cheers,
> 
> David / dhildenb
> 

  reply	other threads:[~2025-06-19  8:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 11:58 [PATCH v2 00/14] mm: Remove pXX_devmap page table bit and pfn_t type Alistair Popple
2025-06-16 11:58 ` [PATCH v2 01/14] mm: Convert pXd_devmap checks to vma_is_dax Alistair Popple
2025-06-17  9:19   ` David Hildenbrand
2025-06-19  8:40     ` Alistair Popple
2025-06-16 11:58 ` [PATCH v2 02/14] mm: Filter zone device pages returned from folio_walk_start() Alistair Popple
2025-06-17  9:25   ` David Hildenbrand
2025-06-17  9:30     ` David Hildenbrand
2025-06-19  0:41       ` Alistair Popple
2025-06-16 11:58 ` [PATCH v2 03/14] mm: Convert vmf_insert_mixed() from using pte_devmap to pte_special Alistair Popple
2025-06-17  9:49   ` David Hildenbrand
2025-06-18  9:31     ` David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 04/14] mm: Remove remaining uses of PFN_DEV Alistair Popple
2025-06-16 11:58 ` [PATCH v2 05/14] mm/gup: Remove pXX_devmap usage from get_user_pages() Alistair Popple
2025-06-16 11:58 ` [PATCH v2 06/14] mm/huge_memory: Remove pXd_devmap usage from insert_pXd_pfn() Alistair Popple
2025-06-17  9:49   ` David Hildenbrand
2025-06-19  8:52     ` Alistair Popple [this message]
2025-06-16 11:58 ` [PATCH v2 07/14] mm: Remove redundant pXd_devmap calls Alistair Popple
2025-06-16 11:58 ` [PATCH v2 08/14] mm/khugepaged: Remove redundant pmd_devmap() check Alistair Popple
2025-06-17  9:44   ` David Hildenbrand
2025-06-19  7:56     ` Alistair Popple
2025-06-16 11:58 ` [PATCH v2 09/14] powerpc: Remove checks for devmap pages and PMDs/PUDs Alistair Popple
2025-06-17  9:37   ` David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 10/14] fs/dax: Remove FS_DAX_LIMITED config option Alistair Popple
2025-06-17  9:37   ` David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 11/14] mm: Remove devmap related functions and page table bits Alistair Popple
2025-06-17  9:36   ` David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 12/14] mm: Remove PFN_MAP, PFN_SPECIAL, PFN_SG_CHAIN and PFN_SG_LAST Alistair Popple
2025-06-16 11:58 ` [PATCH v2 13/14] mm: Remove callers of pfn_t functionality Alistair Popple
2025-06-17  9:35   ` David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 14/14] mm/memremap: Remove unused devmap_managed_key Alistair Popple
2025-06-17  9:34   ` David Hildenbrand

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=esagpnu4oqjpfhvvzfhg6ux5pbikalurex7aw3lelwto4qqzft@vsgljrouwuv7 \
    --to=apopple@nvidia.com \
    --cc=John@groves.net \
    --cc=akpm@linux-foundation.org \
    --cc=balbirs@nvidia.com \
    --cc=bjorn@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=debug@rivosinc.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=jgg@ziepe.ca \
    --cc=jhubbard@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loongarch@lists.linux.dev \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=m.szyprowski@samsung.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=willy@infradead.org \
    --cc=zhang.lyra@gmail.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;
as well as URLs for NNTP newsgroup(s).