From: Mike Rapoport <rppt@kernel.org>
To: Muchun Song <songmuchun@bytedance.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
Arnd Bergmann <arnd@arndb.de>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
Helge Deller <deller@gmx.de>,
linux-mm@kvack.org, linux-arch@vger.kernel.org,
loongarch@lists.linux.dev, linux-mips@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] mm: Generalize page table allocation helpers
Date: Thu, 15 Oct 2026 11:33:25 +0300 [thread overview]
Message-ID: <atCP1YszjrtrB30U@kernel.org> (raw)
In-Reply-To: <20261014035910.687847-1-songmuchun@bytedance.com>
On Wed, Oct 14, 2026 at 11:59:07AM +0800, Muchun Song wrote:
> A subsequent series will switch runtime vmemmap population to the
> generic page-table allocators. Since vmemmap tables belong to init_mm,
> the allocators must select GFP_PGTABLE_KERNEL and mark the ptdesc as a
> kernel page table.
>
> Some architecture-specific allocators do not preserve both semantics.
> LoongArch and MIPS choose PMD/PUD GFP flags without checking the mm,
> which can charge kernel PMD tables to a memcg and leave user PUD tables
> unaccounted. The private PMD/PUD allocators also omit kernel ptdesc
> marking.
>
> Rather than duplicate this handling in each architecture, extend the
> generic PTE, PMD and PUD allocators to support architecture
> initialization hooks and non-zero table orders. LoongArch, MIPS and
> parisc can then drop their private allocators and inherit the generic
> GFP selection and ptdesc handling.
>
> This series only prepares the allocation interfaces; the runtime
> vmemmap conversion will be submitted separately.
>
> Muchun Song (3):
> mm: generalize kernel PTE table allocation
> mm: generalize PMD page table allocation
> mm: generalize PUD page table allocation
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> arch/loongarch/include/asm/pgalloc.h | 48 ----------------------------
> arch/mips/include/asm/pgalloc.h | 40 -----------------------
> arch/parisc/include/asm/pgalloc.h | 17 ----------
> include/asm-generic/pgalloc.h | 29 ++++++++++++++---
> 4 files changed, 24 insertions(+), 110 deletions(-)
>
>
> base-commit: ad9f2d463666c64e94b04be5263c9bf8f9f96fb7
> --
> 2.54.0
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-10-15 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 3:59 [PATCH 0/3] mm: Generalize page table allocation helpers Muchun Song
2026-10-14 3:59 ` [PATCH 1/3] mm: generalize kernel PTE table allocation Muchun Song
2026-10-14 3:59 ` [PATCH 2/3] mm: generalize PMD page " Muchun Song
2026-10-14 3:59 ` [PATCH 3/3] mm: generalize PUD " Muchun Song
2026-10-15 8:33 ` Mike Rapoport [this message]
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=atCP1YszjrtrB30U@kernel.org \
--to=rppt@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=david@kernel.org \
--cc=deller@gmx.de \
--cc=kernel@xen0n.name \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=muchun.song@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=tsbogend@alpha.franken.de \
/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.