public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb+git@google.com>
To: linux-efi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	 Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 0/7] x86/efi: Prepwork for memory map cleanup
Date: Fri, 10 Apr 2026 09:59:50 +0200	[thread overview]
Message-ID: <20260410075950.1687350-9-ardb+git@google.com> (raw)

From: Ard Biesheuvel <ardb@kernel.org>

This is a follow-up to [0], which had some fundamental issues, as
spotted by Sashiko [1]. Disentangling the EFI memory map mess on x86
needs a rethink, but some of the prepwork is still worthwhile, and so it
is presented here separately.

The end goal is still the same, i.e., to remove the need for the x86
boot code to modify the EFI memory map, or reallocate/copy/remap it
numerous times.


[0] https://lore.kernel.org/all/20260319090529.1091660-21-ardb+git@google.com/
[1] https://sashiko.dev/#/patchset/20260319090529.1091660-21-ardb%2Bgit%40google.com

Ard Biesheuvel (7):
  x86/efi: Omit redundant kernel image overlap check
  x86/efi: Drop redundant EFI_PARAVIRT check
  x86/efi: Only merge EFI memory map entries on 32-bit systems
  x86/efi: Defer sub-1M check from unmap to free stage
  x86/efi: Simplify real mode trampoline allocation quirk
  x86/efi: Unmap kernel-reserved boot regions from EFI page tables
  x86/efi: Drop EFI_MEMORY_RUNTIME check from __ioremap_check_other()

 arch/x86/include/asm/efi.h     |  6 ++
 arch/x86/mm/ioremap.c          |  7 +-
 arch/x86/platform/efi/efi.c    | 39 +---------
 arch/x86/platform/efi/efi_32.c | 31 ++++++++
 arch/x86/platform/efi/quirks.c | 78 +++++++-------------
 5 files changed, 69 insertions(+), 92 deletions(-)


base-commit: 259e3e6f9382b6a9fe570313d97c59a233f7d72f
-- 
2.53.0.1213.gd9a14994de-goog


             reply	other threads:[~2026-04-10  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  7:59 Ard Biesheuvel [this message]
2026-04-10  7:59 ` [PATCH 1/7] x86/efi: Omit redundant kernel image overlap check Ard Biesheuvel
2026-04-10  7:59 ` [PATCH 2/7] x86/efi: Drop redundant EFI_PARAVIRT check Ard Biesheuvel
2026-04-10 11:36   ` Thomas Huth
2026-04-10  7:59 ` [PATCH 3/7] x86/efi: Only merge EFI memory map entries on 32-bit systems Ard Biesheuvel
2026-04-10  7:59 ` [PATCH 4/7] x86/efi: Defer sub-1M check from unmap to free stage Ard Biesheuvel
2026-04-10  7:59 ` [PATCH 5/7] x86/efi: Simplify real mode trampoline allocation quirk Ard Biesheuvel
2026-04-10  7:59 ` [PATCH 6/7] x86/efi: Unmap kernel-reserved boot regions from EFI page tables Ard Biesheuvel
2026-04-10  7:59 ` [PATCH 7/7] x86/efi: Drop EFI_MEMORY_RUNTIME check from __ioremap_check_other() Ard Biesheuvel

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=20260410075950.1687350-9-ardb+git@google.com \
    --to=ardb+git@google.com \
    --cc=ardb@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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