linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, kernel-dev@igalia.com,
	kernel@gpiccoli.net, "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Rapoport <rppt@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	SeongJae Park <sj@kernel.org>
Subject: [PATCH v3 0/2] Small improvements to reserve_mem, 3rd attempt
Date: Wed, 18 Mar 2026 15:56:31 -0300	[thread overview]
Message-ID: <20260318190816.1811325-1-gpiccoli@igalia.com> (raw)

Hi folks, this the 3rd iteration of this patchset.

tl; dr: we are adding here error messages in case of failures when
reserve_mem parameter is used, and also a debugfs file to show
successful reservations, with name and size as passed in the cmdline.

More details and history, please take a look at:

V2: lore.kernel.org/r/20260304203300.1414286-2-gpiccoli@igalia.com/
V1: lore.kernel.org/r/20260217195816.861684-1-gpiccoli@igalia.com/

Special thanks to Mike and SJ for the reviews =)
Thanks in advance for suggestions / reviews.
Cheers,

Guilherme G. Piccoli (2):
  mm/memblock: Print out errors on reserve_mem parser
  mm/memblock: Add reserve_mem debugfs info

 mm/memblock.c                                 | 83 +++++++++++++++----
 tools/testing/memblock/linux/string_helpers.h | 10 +++
 2 files changed, 76 insertions(+), 17 deletions(-)
 create mode 100644 tools/testing/memblock/linux/string_helpers.h

-- 
2.50.1



             reply	other threads:[~2026-03-18 19:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 18:56 Guilherme G. Piccoli [this message]
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
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=20260318190816.1811325-1-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 \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox