From: Greg KH <gregkh@linuxfoundation.org>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: stable@vger.kernel.org, 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: Re: [PATCH 6.6 0/3] arm64: Speed up boot with faster linear map creation
Date: Tue, 17 Feb 2026 14:50:14 +0100 [thread overview]
Message-ID: <2026021700-chafe-jurist-cb24@gregkh> (raw)
In-Reply-To: <20260217133411.2881311-1-ryan.roberts@arm.com>
On Tue, Feb 17, 2026 at 01:34:05PM +0000, Ryan Roberts wrote:
> Hi All,
>
> This series is a backport that applies to stable kernel 6.6 (base v6.6.126), 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.
Why can't they just use a newer kernel version (i.e. 6.12)? Surely they
would be able to justify moving to a newer kernel for performance
reasons, why enable them to stay on an older one, just delaying the
inevitable upgrade they will have to do anyway in a year or so?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-17 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 13:34 [PATCH 6.6 0/3] arm64: Speed up boot with faster linear map creation Ryan Roberts
2026-02-17 13:34 ` [PATCH 6.6 1/3] arm64: mm: Don't remap pgtables per-cont(pte|pmd) block Ryan Roberts
2026-02-17 13:34 ` [PATCH 6.6 2/3] arm64: mm: Batch dsb and isb when populating pgtables Ryan Roberts
2026-02-17 13:34 ` [PATCH 6.6 3/3] arm64: mm: Don't remap pgtables for allocate vs populate Ryan Roberts
2026-02-17 13:50 ` Greg KH [this message]
2026-02-17 13:58 ` [PATCH 6.6 0/3] arm64: Speed up boot with faster linear map creation Ryan Roberts
2026-02-17 14:10 ` Greg KH
2026-02-17 14:21 ` Ryan Roberts
2026-02-17 14:26 ` Greg KH
2026-02-17 14:43 ` Ryan Roberts
2026-02-18 9:33 ` Ryan Roberts
2026-02-17 14:27 ` Chen-Yu Tsai
2026-02-18 19:49 ` Noah Meyerhans
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=2026021700-chafe-jurist-cb24@gregkh \
--to=gregkh@linuxfoundation.org \
--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=ryan.roberts@arm.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