linux-kernel - Re: [PATCH] sparc: Use vmemmap_populate_hugepages for vmemmap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAAWJmAa44SF=dj+FTiXn0aZwLLGbSTAieb8Cy73RE0sGAkAYLQ@mail.gmail.com>
Date: Thu, 18 Dec 2025 20:29:27 +0800
From: Tao pilgrim <pilgrimtao@...il.com>
To: Mike Rapoport <rppt@...nel.org>
Cc: davem@...emloft.net, andreas@...sler.com, akpm@...ux-foundation.org, 
	david@...nel.org, lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, 
	vbabka@...e.cz, surenb@...gle.com, mhocko@...e.com, kevin.brodsky@....com, 
	dave.hansen@...ux.intel.com, ziy@...dia.com, chengkaitao@...inos.cn, 
	willy@...radead.org, zhengqi.arch@...edance.com, sparclinux@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] sparc: Use vmemmap_populate_hugepages for vmemmap_populate

On Thu, Dec 18, 2025 at 8:11 PM Mike Rapoport <rppt@...nel.org> wrote:
>
> On Thu, Dec 18, 2025 at 07:45:52PM +0800, Tao pilgrim wrote:
> > On Thu, Dec 18, 2025 at 7:14 PM Mike Rapoport <rppt@...nel.org> wrote:
> > >
> > > On Wed, Dec 17, 2025 at 08:08:58PM +0800, chengkaitao wrote:
> > > > From: Chengkaitao <chengkaitao@...inos.cn>
> > > >
> > > > 1. Added the vmemmap_false_pmd function to accommodate architectures
> > > > that do not support basepages.
> > > > 2. In the SPARC architecture, reimplemented vmemmap_populate using
> > > > vmemmap_populate_hugepages.
> > >
> > > What problem this patch is trying to solve?
> >
> > Following the pattern established by other architectures, vmemmap_populate
> > is reimplemented using vmemmap_populate_hugepages in the SPARC architecture,
> > which fulfills the intended purpose of vmemmap_populate_hugepages.
>
> But what's wrong with the current sparc::vmemmap_populate()?

The current implementation of sparc::vmemmap_populate() is correct
and functional.

However, I believe that generalizing vmemmap_populate_hugepages()
still results in certain architectures requiring special-case handling
branches, which is contrary to our goal of a unified implementation.

Another benefit is that it allows us to eliminate the external
declarations of vmemmap_p?d_populate functions and convert
them to static functions.

> > The functional logic remains unchanged.
> >
> > > > Signed-off-by: Chengkaitao <chengkaitao@...inos.cn>
> > > > ---

-- 
Yours,
Kaitao Cheng