From: chengkaitao <pilgrimtao@gmail.com>
To: davem@davemloft.net, andreas@gaisler.com,
akpm@linux-foundation.org, david@kernel.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
mhocko@suse.com
Cc: kevin.brodsky@arm.com, dave.hansen@linux.intel.com,
ziy@nvidia.com, chengkaitao@kylinos.cn, willy@infradead.org,
zhengqi.arch@bytedance.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
chengkaitao <pilgrimtao@gmail.com>
Subject: [PATCH v3 0/3] Generalize vmemmap_populate_hugepages to sparc
Date: Fri, 19 Dec 2025 01:47:46 +0800 [thread overview]
Message-ID: <20251218174749.45965-1-pilgrimtao@gmail.com> (raw)
Sparc implement vmemmap_populate using vmemmap_populate_hugepages
to streamline the code. Another benefit is that it allows us to
eliminate the external declarations of vmemmap_p?d_populate
functions and convert them to static functions.
Since vmemmap_populate_hugepages may fallback to vmemmap_populate-
_basepages, which differs from sparc's original implementation.
During the v1 discussion with Mike Rapoport, sparc uses base pages
in the kernel page tables, so it should be able to use them in
vmemmap as well. Consequently, no additional special handling is
required.
Remove unnecessary whitespace from sparc.
Changes in v3:
- Allow sparc to fallback to vmemmap_populate_basepages
- Convert vmemmap_p?d_populate() to static functions
- Split the v1 patch
Changes in v2:
- Revert the whitespace deletions
- Change vmemmap_false_pmd to vmemmap_pte_fallback_allowed
Link to V1:
https://lore.kernel.org/all/20251217120858.18713-1-pilgrimtao@gmail.com/
Chengkaitao (3):
sparc: Use vmemmap_populate_hugepages for vmemmap_populate
mm: Convert vmemmap_p?d_populate() to static functions
sparc: Remove unnecessary whitespace
arch/sparc/mm/fault_64.c | 4 +--
arch/sparc/mm/hypersparc.S | 4 +--
arch/sparc/mm/init_64.c | 53 ++++++++++++--------------------------
arch/sparc/mm/io-unit.c | 12 ++++-----
arch/sparc/mm/iommu.c | 2 +-
arch/sparc/mm/swift.S | 2 +-
arch/sparc/mm/ultra.S | 4 +--
include/linux/mm.h | 7 -----
mm/sparse-vmemmap.c | 10 +++----
9 files changed, 36 insertions(+), 62 deletions(-)
--
2.50.1 (Apple Git-155)
next reply other threads:[~2025-12-18 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 17:47 chengkaitao [this message]
2025-12-18 17:47 ` [PATCH v3 1/3] sparc: Use vmemmap_populate_hugepages for vmemmap_populate chengkaitao
2025-12-19 9:33 ` Mike Rapoport
2025-12-18 17:47 ` [PATCH v3 2/3] mm: Convert vmemmap_p?d_populate() to static functions chengkaitao
2025-12-19 9:34 ` Mike Rapoport
2025-12-18 17:47 ` [PATCH v3 3/3] sparc: Remove unnecessary whitespace chengkaitao
2025-12-19 9:29 ` [PATCH v3 0/3] Generalize vmemmap_populate_hugepages to sparc Mike Rapoport
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=20251218174749.45965-1-pilgrimtao@gmail.com \
--to=pilgrimtao@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=chengkaitao@kylinos.cn \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=david@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=zhengqi.arch@bytedance.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