From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
James Gowans <jgowans@amazon.com>,
Mike Rapoport <rppt@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Wei Yang <richard.weiyang@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: updates for 6.11-rc1
Date: Wed, 17 Jul 2024 11:23:50 +0300 [thread overview]
Message-ID: <Zpd_luVnhT7VZz6v@kernel.org> (raw)
Hi Linus,
The following changes since commit c3f38fa61af77b49866b006939479069cd451173:
Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/memblock-v6.11-rc1
for you to fetch changes up to 9364a7e40d54e6858479f0a96e1a04aa1204be16:
memblock tests: fix implicit declaration of function 'numa_valid_node' (2024-07-05 11:24:47 +0300)
----------------------------------------------------------------
memblock: updates for 6.11-rc1
* reserve_mem command line parameter to allow creation of named memory
reservation at boot time.
The driving use-case is to improve the ability of pstore to retain
ramoops data across reboots.
* cleaunps and small improvements in memblock and mm_init
* new tests cases in memblock test suite
----------------------------------------------------------------
James Gowans (1):
memblock: Move late alloc warning down to phys alloc
Steven Rostedt (Google) (2):
mm/memblock: Add "reserve_mem" to reserved named memory at boot up
pstore/ramoops: Add ramoops.mem_name= command line option
Wei Yang (15):
mm/memblock: remove empty dummy entry
memblock tests: add memblock_reserve_all_locations_check()
memblock tests: add memblock_reserve_many_may_conflict_check()
mm/memblock: fix comment for memblock_isolate_range()
memblock tests: add memblock_overlaps_region_checks
mm/memblock: return true directly on finding overlap region
mm/memblock: use PAGE_ALIGN_DOWN to get pgend in free_memmap
mm/mm_init.c: use memblock_region_memory_base_pfn() to get startpfn
mm/memblock: fix a typo in description of for_each_mem_region()
mm/mm_init.c: move nr_initialised reset down a bit
mm/mm_init.c: get the highest zone directly
mm/mm_init.c: use deferred_init_mem_pfn_range_in_zone() to decide loop condition
mm/mm_init.c: not always search next deferred_init_pfn from very beginning
mm/mm_init.c: don't initialize page->lru again
memblock tests: fix implicit declaration of function 'numa_valid_node'
Documentation/admin-guide/kernel-parameters.txt | 22 ++
Documentation/admin-guide/ramoops.rst | 13 +
fs/pstore/ram.c | 14 ++
include/linux/memblock.h | 21 +-
include/linux/mm.h | 2 +
mm/memblock.c | 151 ++++++++++--
mm/mm_init.c | 69 +++---
tools/include/linux/mm.h | 1 +
tools/include/linux/numa.h | 5 +
tools/testing/memblock/tests/basic_api.c | 314 +++++++++++++++++++++++-
tools/testing/memblock/tests/common.c | 8 +-
tools/testing/memblock/tests/common.h | 4 +
12 files changed, 542 insertions(+), 82 deletions(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2024-07-17 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 8:23 Mike Rapoport [this message]
2024-07-18 23:06 ` [GIT PULL] memblock: updates for 6.11-rc1 pr-tracker-bot
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=Zpd_luVnhT7VZz6v@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jgowans@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).