From: Ryan Roberts <ryan.roberts@arm.com>
To: stable@vger.kernel.org
Cc: Ryan Roberts <ryan.roberts@arm.com>,
catalin.marinas@arm.com, will@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Jack Aboutboul <jaboutboul@microsoft.com>,
Sharath George John <sgeorgejohn@microsoft.com>,
Noah Meyerhans <nmeyerhans@microsoft.com>,
Jim Perrin <Jim.Perrin@microsoft.com>
Subject: [PATCH 6.1 0/3] arm64: Speed up boot with faster linear map creation
Date: Tue, 17 Feb 2026 13:35:21 +0000 [thread overview]
Message-ID: <20260217133527.2881603-1-ryan.roberts@arm.com> (raw)
Hi All,
This series is a backport that applies to stable kernel 6.1 (base v6.1.163), for
some speed ups to enable significantly faster booting on systems with a lot of
memory. The patches were originally posted at:
https://lore.kernel.org/linux-arm-kernel/20240412131908.433043-1-ryan.roberts@arm.com/
... and were originally merged upstream in v6.10-rc1.
I'm requesting this be merged to stable on behalf of a partner who wants to get
the benefit of this series in Debian 12.
Thanks,
Ryan
Ryan Roberts (3):
arm64: mm: Don't remap pgtables per-cont(pte|pmd) block
arm64: mm: Batch dsb and isb when populating pgtables
arm64: mm: Don't remap pgtables for allocate vs populate
arch/arm64/include/asm/pgtable.h | 7 ++-
arch/arm64/mm/mmu.c | 92 ++++++++++++++++++--------------
2 files changed, 57 insertions(+), 42 deletions(-)
--
2.43.0
next reply other threads:[~2026-02-17 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 13:35 Ryan Roberts [this message]
2026-02-17 13:35 ` [PATCH 6.1 1/3] arm64: mm: Don't remap pgtables per-cont(pte|pmd) block Ryan Roberts
2026-02-17 13:35 ` [PATCH 6.1 2/3] arm64: mm: Batch dsb and isb when populating pgtables Ryan Roberts
2026-02-17 13:35 ` [PATCH 6.1 3/3] arm64: mm: Don't remap pgtables for allocate vs populate Ryan Roberts
2026-02-17 13:50 ` [PATCH 6.1 0/3] arm64: Speed up boot with faster linear map creation Greg KH
2026-03-19 13:54 ` Greg KH
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=20260217133527.2881603-1-ryan.roberts@arm.com \
--to=ryan.roberts@arm.com \
--cc=Jim.Perrin@microsoft.com \
--cc=catalin.marinas@arm.com \
--cc=jaboutboul@microsoft.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmeyerhans@microsoft.com \
--cc=sgeorgejohn@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=will@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