linux-kernel - Re: [PATCH] mm/hugetlb: skip report_hugepages() output when no hugepages configured

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 for Android: free password hash cracker in your pocket

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

Message-ID: <b5169886-1216-4d49-85f1-437ad7063fd3@redhat.com>
Date: Wed, 10 Sep 2025 11:09:10 +0200
From: David Hildenbrand <david@...hat.com>
To: lirongqing <lirongqing@...du.com>, muchun.song@...ux.dev,
 osalvador@...e.de, akpm@...ux-foundation.org, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/hugetlb: skip report_hugepages() output when no
 hugepages configured

On 10.09.25 11:03, lirongqing wrote:
> From: Li RongQing <lirongqing@...du.com>
> 
> Avoid unnecessary report_hugepages() output and processing when
> max_huge_pages is 0. This eliminates redundant log messages for
> unconfigured hugepage sizes and saves CPU cycles during boot.
> 
> Before this change, the kernel would always print registration messages
> even for hugepage sizes with zero pre-allocated pages:
> 
> [    4.118953] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
> [    4.122920] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
> [    4.126920] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
> [    4.130920] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
> 
> Now these messages are suppressed when no pages are configured.

Well, there is valuable information in there, especially given that we 
can allocate these hugetlb pages later.

So I think we want to keep printing that information.

-- 
Cheers

David / dhildenb