From: Mike Rapoport <rppt@kernel.org>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
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>,
SeongJae Park <sj@kernel.org>
Subject: Re: [PATCH v3 2/2] mm/memblock: Add reserve_mem debugfs info
Date: Thu, 19 Mar 2026 18:34:57 +0200 [thread overview]
Message-ID: <abwlsdgNWtDeasLT@kernel.org> (raw)
In-Reply-To: <20260318190816.1811325-3-gpiccoli@igalia.com>
On Wed, Mar 18, 2026 at 03:56:33PM -0300, Guilherme G. Piccoli wrote:
> When using the "reserve_mem" parameter, users aim at having an
> area that (hopefully) persists across boots, so pstore infrastructure
> (like ramoops module) can make use of that to save oops/ftrace logs,
> for example.
>
> There is no easy way to determine if this kernel parameter is properly
> set though; the kernel doesn't show information about this memory in
> memblock debugfs, neither in /proc/iomem nor dmesg. This is a relevant
> information for tools like kdumpst[0], to determine if it's reliable
> to use the reserved area as ramoops persistent storage; checking only
> /proc/cmdline is not sufficient as it doesn't tell if the reservation
> effectively succeeded or not.
>
> Add here a new file under memblock debugfs showing properly set memory
> reservations, with name and size as passed to "reserve_mem". Notice that
> if no "reserve_mem=" is passed on command-line or if the reservation
> attempts fail, the file is not created.
...
> -static int __init memblock_init_debugfs(void)
> +static inline void memblock_debugfs_make_dirs(struct dentry *root)
This does not make dirs but rather exposes files representing memblock
arrays.
How about calling this function
memblock_debugfs_expose_arrays()?
> {
> - struct dentry *root = debugfs_create_dir("memblock", NULL);
> -
> - debugfs_create_file("memory", 0444, root,
> - &memblock.memory, &memblock_debug_fops);
> - debugfs_create_file("reserved", 0444, root,
> - &memblock.reserved, &memblock_debug_fops);
> #ifdef CONFIG_HAVE_MEMBLOCK_PHYS_MAP
> debugfs_create_file("physmem", 0444, root, &physmem,
> &memblock_debug_fops);
> #endif
> + debugfs_create_file("memory", 0444, root,
> + &memblock.memory, &memblock_debug_fops);
> + debugfs_create_file("reserved", 0444, root,
> + &memblock.reserved, &memblock_debug_fops);
No need to move these after PHYS_MAP attribute
> +}
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-03-19 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 18:56 [PATCH v3 0/2] Small improvements to reserve_mem, 3rd attempt Guilherme G. Piccoli
2026-03-18 18:56 ` [PATCH v3 1/2] mm/memblock: Print out errors on reserve_mem parser Guilherme G. Piccoli
2026-03-18 18:56 ` [PATCH v3 2/2] mm/memblock: Add reserve_mem debugfs info Guilherme G. Piccoli
2026-03-19 16:34 ` Mike Rapoport [this message]
2026-03-19 17:14 ` Guilherme G. Piccoli
2026-03-19 18:01 ` Mike Rapoport
2026-03-24 1:22 ` [PATCH v4 1/2] mm/memblock: Print out errors on reserve_mem parser Guilherme G. Piccoli
2026-03-24 1:22 ` [PATCH v4 2/2] mm/memblock: Add reserve_mem debugfs info Guilherme G. Piccoli
2026-03-25 1:24 ` SeongJae Park
2026-03-24 15:17 ` [PATCH v3 0/2] Small improvements to reserve_mem, 3rd attempt 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=abwlsdgNWtDeasLT@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gpiccoli@igalia.com \
--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=sj@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 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.