From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock updates for v7.1-rc1
Date: Sat, 18 Apr 2026 12:00:06 +0300 [thread overview]
Message-ID: <aeNIFuabuGbdVvDW@kernel.org> (raw)
Hi Linus,
The following changes since commit f338e77383789c0cae23ca3d48adcc5e9e137e3c:
Linux 7.0-rc4 (2026-03-15 13:52:05 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/memblock-v7.1-rc1
for you to fetch changes up to d5759519805c54786c00765ca1303e6d7a0676ca:
x86/alternative: delay freeing of smp_locks section (2026-04-03 17:38:34 +0300)
----------------------------------------------------------------
memblock: updates for 7.0-rc1
* improve debugability of reserve_mem kernel parameter handling with print
outs in case of a failure and debugfs info showing what was actually
reserved
* Make memblock_free_late() and free_reserved_area() use the same core
logic for freeing the memory to buddy and ensure it takes care of
updating memblock arrays when ARCH_KEEP_MEMBLOCK is enabled.
----------------------------------------------------------------
Guilherme G. Piccoli (2):
memblock: Print out errors on reserve_mem parser
memblock: Add reserve_mem debugfs info
Mike Rapoport (Microsoft) (11):
memblock: move reserve_bootmem_range() to memblock.c and make it static
memblock: reserve_mem: fix end caclulation in reserve_mem_release_by_name()
powerpc: fadump: pair alloc_pages_exact() with free_pages_exact()
powerpc: opal-core: pair alloc_pages_exact() with free_pages_exact()
mm: move free_reserved_area() to mm/memblock.c
memblock: make free_reserved_area() more robust
memblock: extract page freeing from free_reserved_area() into a helper
memblock: make free_reserved_area() update memblock if ARCH_KEEP_MEMBLOCK=y
memblock, treewide: make memblock_free() handle late freeing
memblock: warn when freeing reserved memory before memory map is initialized
x86/alternative: delay freeing of smp_locks section
arch/arm64/mm/init.c | 3 -
arch/powerpc/kernel/fadump.c | 16 +-
arch/powerpc/platforms/powernv/opal-core.c | 11 +-
arch/sparc/kernel/mdesc.c | 4 +-
arch/x86/kernel/alternative.c | 22 ++-
arch/x86/kernel/setup.c | 2 +-
arch/x86/platform/efi/memmap.c | 5 +-
arch/x86/platform/efi/quirks.c | 2 +-
drivers/firmware/efi/apple-properties.c | 2 +-
drivers/of/kexec.c | 2 +-
include/linux/bootmem_info.h | 4 -
include/linux/memblock.h | 2 -
include/linux/mm.h | 3 -
init/initramfs.c | 7 -
kernel/dma/swiotlb.c | 6 +-
lib/bootconfig.c | 2 +-
mm/internal.h | 10 ++
mm/kfence/core.c | 4 +-
mm/memblock.c | 231 ++++++++++++++++++++------
mm/mm_init.c | 25 ---
mm/page_alloc.c | 46 -----
tools/include/linux/mm.h | 3 +-
tools/testing/memblock/internal.h | 43 ++++-
tools/testing/memblock/linux/string_helpers.h | 10 ++
tools/testing/memblock/mmzone.c | 4 -
25 files changed, 271 insertions(+), 198 deletions(-)
create mode 100644 tools/testing/memblock/linux/string_helpers.h
--
Sincerely yours,
Mike.
reply other threads:[~2026-04-18 9:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aeNIFuabuGbdVvDW@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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