[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAWJmAaxtKY50BEm3N8V1QTwpyCgQLfLFarrVfPVVpXg9ftmcw@mail.gmail.com>
Date: Thu, 18 Dec 2025 19:45:52 +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 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.
The functional logic remains unchanged.
> > Signed-off-by: Chengkaitao <chengkaitao@...inos.cn>
> > ---
--
Yours,
Kaitao Cheng
Powered by blists - more mailing lists