From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"David Hildenbrand (Arm)" <david@kernel.org>
Subject: [GIT PULL] Core MM updates for 7.4 (new MM tree)
Date: Fri, 23 Oct 2026 19:20:58 +0200 [thread overview]
Message-ID: <20261023172100.49643-1-david@kernel.org> (raw)
Hi Linus,
As discussed at the Maintainer Summit, this is the first pull request from
the new core MM tree. I'm a bit late due to travel.
This cycle was primarily used to set up the core MM tree, move some
smaller MM components into it, and establish the MM integration workflow
for linux-next.
For 7.4, MM updates will reach you through the slab, memblock, Andrew's
MM, and my core MM trees.
For the next cycle (7.5), we plan to route fewer patches through Andrew's
tree and start merging the MM component trees (memblock, slab, core) into
the new MM integration tree for upstreaming.
In subsequent cycles, we'll gradually move more components from
Andrew's MM tree into existing or new MM component trees, with the
eventual goal of having a single MM integration tree for you to pull
from.
I'm using merge commits to:
- Merge patch series, with the adjusted cover letter in the merge
commit message.
- Merge topic branches, with a summary of the changes in the merge
commit message.
The signed tag contains a high-level summary of the changes.
Please let me know if anything looks odd or if you would prefer different
summaries.
There are no known conflicts with other trees.
Cheers,
David
----------------------------------------------------------------
The following changes since commit 93f51579e7df248780214094418f205253383cc5:
Linux 7.3-rc4 (2026-09-20 13:48:15 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mm/core.git tags/mm-core-7.4-rc1
for you to fetch changes up to 07ae95d933b84db98696f23e24de078b251561ff:
Merge 'memhp-7.4.misc' (2026-10-18 10:26:46 +0200)
----------------------------------------------------------------
Core memory management updates for 7.4
This includes updates to:
- MEMHP (Memory Hotplug)
- GUP (Get User Pages)
The main change is:
- Reduce zone contiguity checking overhead during memory
hot(un)plug (Yuan Liu)
Other changes include smaller fixes along with various cleanups.
Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
----------------------------------------------------------------
Aristeu Rozanski (2):
mm: gup: move pmd_protnone() into gup_fast_pmd_leaf()
mm: gup: cleanup the gup_fast_*() call chain
David Hildenbrand (Arm) (5):
Merge patch series "mm: gup: cleanup gup_fast call chain"
mm/memory_hotplug: make shrink_zone_span() more robust
Merge patch series "mm/memory_hotplug: optimize zone contiguous check when changing pfn range"
Merge 'gup-7.4.misc'
Merge 'memhp-7.4.misc'
Greg Kroah-Hartman (1):
mm/gup: honour FOLL_PIN in NOMMU __get_user_pages_locked()
Lance Yang (1):
mm/memory_hotplug: fix missing rollback in __add_pages()
Sarthak Sharma (2):
mm/gup_test: safely calculate GUP batch size
mm/gup_test: report actual pinned bytes
Yuan Liu (1):
mm/memory_hotplug: optimize zone contiguous check when changing pfn range
Documentation/mm/physical_memory.rst | 6 ++
drivers/base/memory.c | 7 +-
include/linux/mmzone.h | 69 ++++++++++++
mm/gup.c | 204 +++++++++++++++++++----------------
mm/gup_test.c | 11 +-
mm/memory_hotplug.c | 77 ++++++-------
mm/mm_init.c | 64 ++++++-----
mm/mm_init.h | 6 --
mm/page_alloc.h | 2 +-
9 files changed, 266 insertions(+), 180 deletions(-)
next reply other threads:[~2026-10-23 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 17:20 David Hildenbrand (Arm) [this message]
2026-10-23 19:58 ` 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=20261023172100.49643-1-david@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@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
all inboxes | Powered by JetHome®