linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	kernel-dev@igalia.com, kernel@gpiccoli.net,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 2/2] mm/memblock: Add reserve_mem debugfs info
Date: Sun, 22 Feb 2026 17:18:38 -0300	[thread overview]
Message-ID: <34de3a3c-dc04-a9a8-d90f-afa4199e0168@igalia.com> (raw)
In-Reply-To: <aZtWrjlAaljQ1F48@kernel.org>

On 22/02/2026 16:19, Mike Rapoport wrote:
> [...]
>> First of all, what should we do regarding patch 1? Should I resubmit as
>> part of V2, even with no changes - or pick it now and I only submit
>> patch 2 as V2, with changes?
>  
> Please resend both patches together. 
>

Hi Mike! OK, thanks.


>> [...]
>> Specifically here, by magic number you mean my choice of 16, right? What
>> do you suggest me to pick? It's the length of the string carrying the
>> size of reserved_mem, some number must be selected for this
>> length...lemme know WDYT.
>  
> sizeof(txtsz) should work :) 
>

Ahh OK heh
I thought you were not happy with 16 as the size (this is an arbitrary
number itself), but it's just on the func argument - cool, will fix it!


>>> [...] 
>> Very good suggestions here, but just let me clarify: so I could continue
>> showing the "reserved_mem_param" inside the "<debugfs>/memblock" folder,
>> just using a different function for that attribute?
> 
> Yes, something like
> 
> static int memblock_reserve_mem_show(struct seq_file *m, void *private)
> {
> 	...
> }
> DEFINE_SHOW_ATTRIBUTE(memblock_reserve_mem);
>  
>> I understood that, based on your (good) suggestion to hide the memblock
>> folder if ARCH_KEEP_MEMBLOCK is not defined and there is no reserved_mem
>> set ... just want to confirm to follow-up the implementation.
> 
> Yes, that's what I meant.
> 

Great, thanks a lot again!
Cheers,


Guilherme


  reply	other threads:[~2026-02-22 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 19:45 [PATCH 0/2] Some small improvements to reserve_mem Guilherme G. Piccoli
2026-02-17 19:45 ` [PATCH 1/2] mm/memblock: Print out errors on reserve_mem parser Guilherme G. Piccoli
2026-02-17 19:45 ` [PATCH 2/2] mm/memblock: Add reserve_mem debugfs info Guilherme G. Piccoli
2026-02-18  0:15   ` kernel test robot
2026-02-18  0:26   ` kernel test robot
2026-02-21  8:52   ` Mike Rapoport
2026-02-22 13:58     ` Guilherme G. Piccoli
2026-02-22 19:19       ` Mike Rapoport
2026-02-22 20:18         ` Guilherme G. Piccoli [this message]
2026-02-21  8:29 ` [PATCH 0/2] Some small improvements to reserve_mem 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=34de3a3c-dc04-a9a8-d90f-afa4199e0168@igalia.com \
    --to=gpiccoli@igalia.com \
    --cc=akpm@linux-foundation.org \
    --cc=kernel-dev@igalia.com \
    --cc=kernel@gpiccoli.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rostedt@goodmis.org \
    --cc=rppt@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