From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: linux-mm@kvack.org, rppt@kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-dev@igalia.com,
kernel@gpiccoli.net, gpiccoli@igalia.com,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH V2 0/2] Small improvements to reserve_mem, take 2
Date: Wed, 4 Mar 2026 17:14:09 -0300 [thread overview]
Message-ID: <20260304203300.1414286-2-gpiccoli@igalia.com> (raw)
Hi folks, this is the 2nd version of the patchset, V1 is
here: https://lore.kernel.org/r/20260217195816.861684-1-gpiccoli@igalia.com/
So, quick summary: we are adding
(a) Error messages if "reserve_mem=" fails;
(b) A debugfs file in case "reserve_mem=" succeeds, showing name and
size of the allocation.
Use case of (a) is kinda obvious - we want to know if there are failures.
Use case for (b) are users or tools like kdumpst[0] that might want to
check if their reserve_mem allocation(s) succeeded in order to load
ramoops with proper parameters, using the reserved areas.
Thanks a lot Mike for the great review so far! Questions or comments
are welcome,
Guilherme G. Piccoli (2):
mm/memblock: Print out errors on reserve_mem parser
mm/memblock: Add reserve_mem debugfs info
mm/memblock.c | 65 ++++++++++++++++++++++++++++++++++++++++++---------
1 file changed, 54 insertions(+), 11 deletions(-)
[0] https://aur.archlinux.org/packages/kdumpst
--
2.50.1
next reply other threads:[~2026-03-04 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 20:14 Guilherme G. Piccoli [this message]
2026-03-04 20:14 ` [PATCH V2 1/2] mm/memblock: Print out errors on reserve_mem parser Guilherme G. Piccoli
2026-03-04 20:14 ` [PATCH V2 2/2] mm/memblock: Add reserve_mem debugfs info Guilherme G. Piccoli
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=20260304203300.1414286-2-gpiccoli@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