Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Muchun Song <songmuchun@bytedance.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Oscar Salvador <osalvador@suse.de>,
	Mike Rapoport <rppt@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
	David Laight <david.laight.linux@gmail.com>,
	"Liam R . Howlett" <liam@infradead.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Qi Zheng <qi.zheng@linux.dev>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 09/17] mm/sparse: initialize memory sections earlier
Date: Wed, 9 Sep 2026 20:29:23 +0800	[thread overview]
Message-ID: <E54037CE-6CE6-41AB-A525-8BDCE55996AC@linux.dev> (raw)
In-Reply-To: <a2016390-28ce-4199-a063-d2e9101dacab@kernel.org>



> On Sep 9, 2026, at 17:56, David Hildenbrand (Arm) <david@kernel.org> wrote:
> 
> On 8/25/26 10:46, Muchun Song wrote:
>> Upcoming HugeTLB bootmem changes need sparsemem section metadata before
>> the HugeTLB bootmem allocation path runs. The memory sections are
>> initialized from sparse_init(), which is called too late for that setup.
>> 
>> Move the code that initializes sparsemem section metadata for memblock
>> ranges into mm_core_init_early(), before free_area_init() and the HugeTLB
>> bootmem setup. Rename the helper to sparse_sections_init() so the new
>> caller describes the sparsemem-specific initialization step.
>> 
>> This is a preparatory change.
>> 
>> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
>> Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>> ---
>> v5:
>> - Collect Reviewed-by from Mike Rapoport
>> 
>> v2:
>> - Rename the helper to sparse_sections_init() to describe the section
>>  metadata initialization (suggested by Mike Rapoport)
>> - Fix the !SPARSEMEM stub name so SPARSEMEM=n builds compile
>>  (reported by Sashiko)
>> ---
>> mm/mm_init.c |  1 +
>> mm/sparse.c  | 10 ++--------
>> mm/sparse.h  |  2 ++
>> 3 files changed, 5 insertions(+), 8 deletions(-)
>> 
>> diff --git a/mm/mm_init.c b/mm/mm_init.c
>> index 0317fb781e77..e2a16d833635 100644
>> --- a/mm/mm_init.c
>> +++ b/mm/mm_init.c
>> @@ -2642,6 +2642,7 @@ void __init mm_core_init_early(void)
>> {
>> 	kho_memory_init_early();
>> 
>> + 	sparse_sections_init();
>> 	free_area_init();
>> 
>> hugetlb_cma_reserve();
>> diff --git a/mm/sparse.c b/mm/sparse.c
>> index e6cb67ca9c8d..439802e6a6ad 100644
>> --- a/mm/sparse.c
>> +++ b/mm/sparse.c
>> @@ -191,12 +191,8 @@ static void __init memory_present(int nid, unsigned long start, unsigned long en
>> }
>> }
>> 
>> -/*
>> - * Mark all memblocks as present using memory_present().
>> - * This is a convenience function that is useful to mark all of the systems
>> - * memory as present during initialization.
>> - */
>> -static void __init memblocks_present(void)
>> +/* Initialize memory section metadata for all system memory. */
> 
> I'd drop this comment, it's not entirely accurate. A lot more initialization of
> the sections happens later.

I can drop this line comment.

> 
> What this function mostly does is
> 
> (a) Allocate sparse-exteme metadata
> (b) Temporarily store the nid and mark the section for being present and online

Yes.

> 
> I have patches to get rid of __section_mark_present() and just set them all to
> SECTION_IS_EARLY|SECTION_IS_ONLINE such that we can just iterate early sections
> and get rid of that PRESENT monstrosity.
> 
> Apart from that LGTM, even though I don't particularly enjoy splitting us now
> having two init entry points
> 
> sparse_init

Maybe this one should be sparse_memmap_init? If yes, it could be another separate
cleanup patch.

Thanks,
Muchun

> 
> and
> 
> sparse_sections_init
> 
> 
> Where it's rather unclear from the name what is actually happening.
> 
> -- 
> Cheers,
> 
> David




  reply	other threads:[~2026-09-09 12:29 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  8:45 [PATCH v5 00/17] mm: Introduce section-based vmemmap optimization for HugeTLB Muchun Song
2026-08-25  8:45 ` [PATCH v5 01/17] mm/sparse: relax struct mem_section size constraints Muchun Song
2026-09-09  9:33   ` David Hildenbrand (Arm)
2026-08-25  8:45 ` [PATCH v5 02/17] mm/sparse-vmemmap: rename HVO order macros Muchun Song
2026-08-25 10:05   ` Qi Zheng
2026-08-25  8:45 ` [PATCH v5 03/17] mm/mm_init: skip initializing shared vmemmap tail pages Muchun Song
2026-08-25  9:30   ` Mike Rapoport
2026-08-25 10:15   ` Qi Zheng
2026-09-09  9:36   ` David Hildenbrand (Arm)
2026-09-09 11:30     ` Muchun Song
2026-08-25  8:45 ` [PATCH v5 04/17] mm/sparse-vmemmap: initialize shared tail vmemmap pages on allocation Muchun Song
2026-08-25  9:30   ` Mike Rapoport
2026-08-25 10:40   ` Qi Zheng
2026-09-09  9:39   ` David Hildenbrand (Arm)
2026-09-09 12:49     ` Muchun Song
2026-08-25  8:45 ` [PATCH v5 05/17] mm/sparse-vmemmap: support section-based vmemmap accounting Muchun Song
2026-08-25 10:47   ` Qi Zheng
2026-08-25  8:45 ` [PATCH v5 06/17] mm/mm_init: factor out pfn_to_zone() Muchun Song
2026-08-25 10:51   ` Qi Zheng
2026-08-25  8:45 ` [PATCH v5 07/17] mm/sparse-vmemmap: move helpers ahead of future callers Muchun Song
2026-08-25 10:54   ` Qi Zheng
2026-08-25  8:45 ` [PATCH v5 08/17] mm/sparse-vmemmap: support section-based vmemmap optimization Muchun Song
2026-08-25  9:30   ` Mike Rapoport
2026-08-25 12:38   ` Qi Zheng
2026-08-25  8:46 ` [PATCH v5 09/17] mm/sparse: initialize memory sections earlier Muchun Song
2026-08-25 12:49   ` Qi Zheng
2026-09-09  9:56   ` David Hildenbrand (Arm)
2026-09-09 12:29     ` Muchun Song [this message]
2026-09-09 12:48       ` David Hildenbrand (Arm)
2026-09-09 12:58         ` Muchun Song
2026-08-25  8:46 ` [PATCH v5 10/17] mm/hugetlb: switch HugeTLB to section-based vmemmap optimization Muchun Song
2026-08-25 13:12   ` Qi Zheng
2026-08-26  2:38     ` Muchun Song
2026-08-26  3:24       ` Qi Zheng
2026-09-09  9:58   ` David Hildenbrand (Arm)
2026-09-09 13:08     ` Muchun Song
2026-09-09 13:39       ` David Hildenbrand (Arm)
2026-08-25  8:46 ` [PATCH v5 11/17] mm/sparse-vmemmap: remove SPARSEMEM_VMEMMAP_PREINIT support Muchun Song
2026-08-25 13:16   ` Qi Zheng
2026-09-09  9:59   ` David Hildenbrand (Arm)
2026-08-25  8:46 ` [PATCH v5 12/17] mm/sparse: inline usemap allocation into sparse_init_nid() Muchun Song
2026-09-09 10:01   ` David Hildenbrand (Arm)
2026-08-25  8:46 ` [PATCH v5 13/17] mm/sparse: remove section_map_size() Muchun Song
2026-09-09 10:02   ` David Hildenbrand (Arm)
2026-08-25  8:46 ` [PATCH v5 14/17] mm/hugetlb: remove HUGE_BOOTMEM_HVO Muchun Song
2026-08-25 13:28   ` Qi Zheng
2026-08-25  8:46 ` [PATCH v5 15/17] mm/hugetlb: remove HUGE_BOOTMEM_CMA Muchun Song
2026-08-25 13:42   ` Qi Zheng
2026-08-25  8:46 ` [PATCH v5 16/17] mm/hugetlb: localize struct huge_bootmem_page Muchun Song
2026-08-25 13:38   ` Qi Zheng
2026-08-25  8:46 ` [PATCH v5 17/17] mm/hugetlb: localize HUGE_BOOTMEM_ZONES_VALID Muchun Song
2026-08-25 13:40   ` Qi Zheng
2026-08-28  4:20 ` [PATCH v5 00/17] mm: Introduce section-based vmemmap optimization for HugeTLB Andrew Morton
2026-09-09  9:31 ` David Hildenbrand (Arm)

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=E54037CE-6CE6-41AB-A525-8BDCE55996AC@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david.laight.linux@gmail.com \
    --cc=david@kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=osalvador@suse.de \
    --cc=qi.zheng@linux.dev \
    --cc=rppt@kernel.org \
    --cc=songmuchun@bytedance.com \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    /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