public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb+git@google.com>
To: linux-kernel@vger.kernel.org
Cc: linux-efi@vger.kernel.org, x86@kernel.org,
	 Ard Biesheuvel <ardb@kernel.org>,
	"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
	 Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: [PATCH v2 07/19] x86/efi: Simplify real mode trampoline allocation quirk
Date: Thu, 19 Mar 2026 10:05:37 +0100	[thread overview]
Message-ID: <20260319090529.1091660-28-ardb+git@google.com> (raw)
In-Reply-To: <20260319090529.1091660-21-ardb+git@google.com>

From: Ard Biesheuvel <ardb@kernel.org>

To work around a common bug in EFI firmware for x86 systems, Linux
reserves all EFI boot services code and data regions until after it has
invoked the SetVirtualAddressMap() EFI runtime service. This is needed
because those regions may still be accessed by the firmware during that
call, even though the EFI spec says that they shouldn't.

This includes any boot services data regions below 1M, which might mean
that by the time the real mode trampoline is being allocated, all memory
below 1M is already exhausted.

Commit

  5bc653b73182 ("x86/efi: Allocate a trampoline if needed in efi_free_boot_services()")

added a quirk to detect this condition, and to make another attempt at
allocating the real mode trampoline when freeing those boot services
regions again. This is a rather crude hack, which gets in the way of
cleanup work on the EFI/x86 memory map handling code.

Given that

- the real mode trampoline is normally allocated soon after all EFI boot
  services regions are reserved temporarily,
- this allocation logic marks all memory below 1M as reserved,
- the trampoline memory is not actually populated until an early
  initcall,

there is actually no need to reserve any boot services regions below 1M,
even if they are mapped into the EFI page tables during the call to
SetVirtualAddressMap(). So cap the lower bound of the reserved regions
to 1M, and fix up the size accordingly when making the reservation. This
allows the additional quirk to be dropped entirely.

Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
---
 arch/x86/platform/efi/quirks.c | 29 ++++----------------
 1 file changed, 6 insertions(+), 23 deletions(-)

diff --git a/arch/x86/platform/efi/quirks.c b/arch/x86/platform/efi/quirks.c
index 25f51d673ad6..c867153eab8a 100644
--- a/arch/x86/platform/efi/quirks.c
+++ b/arch/x86/platform/efi/quirks.c
@@ -329,10 +329,14 @@ void __init efi_reserve_boot_services(void)
 		return;
 
 	for_each_efi_memory_desc(md) {
-		u64 start = md->phys_addr;
-		u64 size = md->num_pages << EFI_PAGE_SHIFT;
+		u64 start = max(md->phys_addr, SZ_1M);
+		u64 end = md->phys_addr + (md->num_pages << EFI_PAGE_SHIFT);
+		u64 size = end - start;
 		bool already_reserved;
 
+		if (end < start)
+			continue;
+
 		if (md->type != EFI_BOOT_SERVICES_CODE &&
 		    md->type != EFI_BOOT_SERVICES_DATA)
 			continue;
@@ -434,7 +438,6 @@ void __init efi_unmap_boot_services(void)
 	for_each_efi_memory_desc(md) {
 		unsigned long long start = md->phys_addr;
 		unsigned long long size = md->num_pages << EFI_PAGE_SHIFT;
-		size_t rm_size;
 
 		if (md->type != EFI_BOOT_SERVICES_CODE &&
 		    md->type != EFI_BOOT_SERVICES_DATA) {
@@ -455,26 +458,6 @@ void __init efi_unmap_boot_services(void)
 			continue;
 		}
 
-		/*
-		 * Nasty quirk: if all sub-1MB memory is used for boot
-		 * services, we can get here without having allocated the
-		 * real mode trampoline.  It's too late to hand boot services
-		 * memory back to the memblock allocator, so instead
-		 * try to manually allocate the trampoline if needed.
-		 *
-		 * I've seen this on a Dell XPS 13 9350 with firmware
-		 * 1.4.4 with SGX enabled booting Linux via Fedora 24's
-		 * grub2-efi on a hard disk.  (And no, I don't know why
-		 * this happened, but Linux should still try to boot rather
-		 * panicking early.)
-		 */
-		rm_size = real_mode_size_needed();
-		if (rm_size && (start + rm_size) < (1<<20) && size >= rm_size) {
-			set_real_mode_mem(start);
-			start += rm_size;
-			size -= rm_size;
-		}
-
 		/*
 		 * With CONFIG_DEFERRED_STRUCT_PAGE_INIT parts of the memory
 		 * map are still not initialized and we can't reliably free
-- 
2.53.0.851.ga537e3e6e9-goog


  parent reply	other threads:[~2026-03-19  9:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19  9:05 [PATCH v2 00/19] efi/x86: Avoid the need to mangle the EFI memory map Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 01/19] memblock: Permit existing reserved regions to be marked RSRV_KERN Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 02/19] efi: Tag memblock reservations of boot services regions as RSRV_KERN Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 03/19] x86/efi: Unmap kernel-reserved boot regions from EFI page tables Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 04/19] x86/efi: Drop EFI_MEMORY_RUNTIME check from __ioremap_check_other() Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 05/19] x86/efi: Omit RSRV_KERN memblock reservations when freeing boot regions Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 06/19] x86/efi: Defer sub-1M check from unmap to free stage Ard Biesheuvel
2026-03-19  9:05 ` Ard Biesheuvel [this message]
2026-03-19  9:05 ` [PATCH v2 08/19] x86/efi: Omit redundant kernel image overlap check Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 09/19] x86/efi: Drop redundant EFI_PARAVIRT check Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 10/19] x86/efi: Do not rely on EFI_MEMORY_RUNTIME bit and avoid entry splitting Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 11/19] efi: Use nr_map not map_end to find the last valid memory map entry Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 12/19] x86/efi: Only merge EFI memory map entries on 32-bit systems Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 13/19] x86/efi: Clean the memory map using iterator and filter API Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 14/19] x86/efi: Update the runtime map in place Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 15/19] x86/efi: Use iterator API when mapping EFI regions for runtime Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 16/19] x86/efi: Reuse memory map instead of reallocating it Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 17/19] x86/efi: Defer compaction of the EFI memory map Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 18/19] x86/efi: Do not abuse RUNTIME bit to mark boot regions as reserved Ard Biesheuvel
2026-03-19  9:05 ` [PATCH v2 19/19] x86/efi: Free unused tail of the EFI memory map Ard Biesheuvel
2026-03-24  9:50 ` [PATCH v2 00/19] efi/x86: Avoid the need to mangle " 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=20260319090529.1091660-28-ardb+git@google.com \
    --to=ardb+git@google.com \
    --cc=ardb@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@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