All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Meijing Zhao <zhaomeijing100@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Wandun Chen <chenwandun@lixiang.com>,
	Meijing Zhao <zhaomeijing@lixiang.com>
Subject: Re: [PATCH v2 RESEND 2/3] mm: memblock: show all region flags in debugfs
Date: Mon, 24 Aug 2026 18:15:13 +0300	[thread overview]
Message-ID: <aoxgAYXqXvs0GFYM@kernel.org> (raw)
In-Reply-To: <20260821020910.3428585-3-zhaomeijing100@gmail.com>

On Fri, Aug 21, 2026 at 10:09:09AM +0800, Meijing Zhao wrote:
> From: Meijing Zhao <zhaomeijing@lixiang.com>
> 
> Commit 493f349e38d0 ("memblock: Add flags and nid info in memblock
> debugfs") made memblock_debug_show() stop after finding the first set
> flag. A memblock region can carry multiple flags, so the remaining flags
> are hidden from debugfs.
> 
> In particular, memory allocated for HugeTLB pages is reserved with both
> MEMBLOCK_RSRV_KERN and MEMBLOCK_RSRV_HUGETLB, but debugfs only reports
> RSV_KERN.
> 
> Walk all bits in the region flags and print every set flag separated by
> "|". Keep walking beyond flagname[] so that a set flag without a known
> name is reported as UNKNOWN rather than silently ignored.
> 
> A HugeTLB reservation is now shown as:
> 
>   RSV_KERN|RSV_HUGETLB
> 
> instead of:
> 
>   RSV_KERN
> 
> Fixes: 493f349e38d0 ("memblock: Add flags and nid info in memblock debugfs")
> Signed-off-by: Meijing Zhao <zhaomeijing@lixiang.com>
> ---
>  mm/memblock.c | 22 ++++++++++++++--------
>  1 file changed, 14 insertions(+), 8 deletions(-)
> 
> diff --git a/mm/memblock.c b/mm/memblock.c
> index f2952d725c10..36a8d2a9378d 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -2895,7 +2895,9 @@ static int memblock_debug_show(struct seq_file *m, void *private)
>  	struct memblock_region *reg;
>  	int i, j, nid;
>  	unsigned int count = ARRAY_SIZE(flagname);
> +	unsigned int flags;
>  	phys_addr_t end;
> +	bool first;
>  
>  	for (i = 0; i < type->cnt; i++) {
>  		reg = &type->regions[i];
> @@ -2909,16 +2911,20 @@ static int memblock_debug_show(struct seq_file *m, void *private)
>  		else
>  			seq_printf(m, "%4c ", 'x');
>  		if (reg->flags) {
> -			for (j = 0; j < count; j++) {
> -				if (reg->flags & (1U << j)) {
> -					seq_printf(m, "%s\n", flagname[j]);
> -					break;
> -				}
> +			flags = reg->flags;
> +			first = true;

first and flags can be declared here.

> +			for (j = 0; flags; j++, flags >>= 1) {
> +				if (!(flags & 1))
> +					continue;
> +				if (!first)
> +					seq_putc(m, '|');
> +				seq_puts(m, j < count && flagname[j] ?
> +					 flagname[j] : "UNKNOWN");

Can we really have both j < count and !flagname[j]?

> +				first = false;
>  			}
> -			if (j == count)
> -				seq_printf(m, "%s\n", "UNKNOWN");
> +			seq_putc(m, '\n');
>  		} else {
> -			seq_printf(m, "%s\n", "NONE");
> +			seq_puts(m, "NONE\n");

No need to change this

>  		}
>  	}
>  	return 0;
> -- 
> 2.25.1
> 

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2026-08-24 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  2:09 [PATCH v2 RESEND 0/3] mm: memblock: fix debugfs flag reporting and synchronization Meijing Zhao
2026-08-21  2:09 ` [PATCH v2 RESEND 1/3] mm: memblock: add missing HugeTLB flag name Meijing Zhao
2026-08-21  2:09 ` [PATCH v2 RESEND 2/3] mm: memblock: show all region flags in debugfs Meijing Zhao
2026-08-24 15:15   ` Mike Rapoport [this message]
2026-08-25  1:56     ` Meijing Zhao
2026-08-21  2:09 ` [PATCH v2 RESEND 3/3] mm: memblock: synchronize debugfs reads with memory hotplug Meijing Zhao
2026-08-25  9:35   ` Mike Rapoport
2026-08-23 14:43 ` [PATCH v2 RESEND 0/3] mm: memblock: fix debugfs flag reporting and synchronization 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=aoxgAYXqXvs0GFYM@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chenwandun@lixiang.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=zhaomeijing100@gmail.com \
    --cc=zhaomeijing@lixiang.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.