From: Ard Biesheuvel <ardb+git@google.com>
To: torvalds@linux-foundation.org
Cc: linux-efi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: [GIT PULL] EFI fixes for v6.14 #1
Date: Fri, 14 Feb 2025 18:52:26 +0100 [thread overview]
Message-ID: <20250214175225.544273-2-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Hi Linus,
Please pull the changes below. While not true fixes, these changes are best
merged asap so they can make their way into the stable kernels. That should
ensure that the new EFI_MEMORY_HOT_PLUGGABLE memory attribute is used
consistently by Linux before it ever turns up in production, ensuring that we
can make meaningful use of it without running the risk of regressing existing
users.
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-fixes-for-v6.14-1
for you to fetch changes up to bbc4578537e350d5bf8a7a2c7d054d6b163b3c41:
efi: Use BIT_ULL() constants for memory attributes (2025-02-04 14:08:22 +0100)
----------------------------------------------------------------
EFI fixes for v6.14 #1
Take the newly introduced EFI_MEMORY_HOT_PLUGGABLE memory attribute into
account when placing the kernel image in memory at boot. Otherwise, the
presence of the kernel image could prevent such a memory region from
being unplugged at runtime if it was 'cold plugged', i.e., already
plugged in at boot time (and exposed via the EFI memory map)
----------------------------------------------------------------
Ard Biesheuvel (2):
efi: Avoid cold plugged memory for placing the kernel
efi: Use BIT_ULL() constants for memory attributes
drivers/firmware/efi/efi.c | 6 ++++--
drivers/firmware/efi/libstub/randomalloc.c | 3 +++
drivers/firmware/efi/libstub/relocate.c | 3 +++
include/linux/efi.h | 31 +++++++++++++++---------------
4 files changed, 26 insertions(+), 17 deletions(-)
next reply other threads:[~2025-02-14 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 17:52 Ard Biesheuvel [this message]
2025-02-14 22:53 ` [GIT PULL] EFI fixes for v6.14 #1 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=20250214175225.544273-2-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.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