From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ardb+git@google.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Kees Cook <kees@kernel.org>
Subject: Re: [RFC PATCH] arm64/mm: Remove randomization of the linear map
Date: Tue, 29 Apr 2025 21:27:43 +0100 [thread overview]
Message-ID: <174592931036.425225.4448190520420242534.b4-ty@kernel.org> (raw)
In-Reply-To: <20250318134949.3194334-2-ardb+git@google.com>
On Tue, 18 Mar 2025 14:49:50 +0100, Ard Biesheuvel wrote:
> Since commit
>
> 97d6786e0669 ("arm64: mm: account for hotplug memory when randomizing the linear region")
>
> the decision whether or not to randomize the placement of the system's
> DRAM inside the linear map is based on the capabilities of the CPU
> rather than how much memory is present at boot time. This change was
> necessary because memory hotplug may result in DRAM appearing in places
> that are not covered by the linear region at all (and therefore
> unusable) if the decision is solely based on the memory map at boot.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64/mm: Remove randomization of the linear map
https://git.kernel.org/arm64/c/1db780bafa4c
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-04-29 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 13:49 [RFC PATCH] arm64/mm: Remove randomization of the linear map Ard Biesheuvel
2025-03-20 7:57 ` Ard Biesheuvel
2025-03-20 11:24 ` Ryan Roberts
2025-04-29 20:27 ` Will Deacon [this message]
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=174592931036.425225.4448190520420242534.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kees@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@arm.com \
/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