From: Pankaj Gupta <pankaj.gupta@amd.com>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>
Cc: "H . Peter Anvin" <hpa@zytor.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ard Biesheuvel <ardb@kernel.org>,
Kiryl Shutsemau <kas@kernel.org>, <linux-kernel@vger.kernel.org>,
Mike Rapoport <rppt@kernel.org>, <linux-mm@kvack.org>,
<Pankaj.gupta@amd.com>, Pankaj Gupta <pankaj.gupta@amd.com>
Subject: [PATCH] x86/unaccepted_memory: Do not accept ranges that are no longer E820 RAM
Date: Mon, 2 Nov 2026 05:31:27 -0600 [thread overview]
Message-ID: <20261102113127.161823-1-pankaj.gupta@amd.com> (raw)
The EFI stub builds the unaccepted memory bitmap before the kernel parses
its command line. Option memmap=<size>$<addr> removes RAM from the E820
map while its bits are still set in the bitmap.
The removed range, such as a memmap=...$... hole, is then still treated as
unaccepted RAM and accept_memory() tries to accept it. The hole is not
mapped, so on SEV-SNP the PVALIDATE faults and the guest crashes early in
the boot:
BUG: unable to handle page fault for address: ffff8a14bfe00000
RIP: 0010:pvalidate_pages+0xc0/0x250
set_pages_state+0x41a/0x440
snp_accept_memory+0x3e/0x50
accept_memory+0x186/0x260
__free_pages_core+0xd2/0x240
memblock_free_pages+0x1b/0x30
memblock_free_all+0x275/0x2d0
This was seen with memmap=2M$0x1ffe00000, a 2 MiB hole in RAM, on a 19 GiB
SNP guest with lazy acceptance.
Fixes: 2053bc57f367 ("efi: Add unaccepted memory support")
Signed-off-by: Pankaj Gupta <pankaj.gupta@amd.com>
---
arch/x86/include/asm/unaccepted_memory.h | 23 ++++++++++++++++++++++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/unaccepted_memory.h b/arch/x86/include/asm/unaccepted_memory.h
index f5937e9866ac..744f1a993352 100644
--- a/arch/x86/include/asm/unaccepted_memory.h
+++ b/arch/x86/include/asm/unaccepted_memory.h
@@ -2,10 +2,11 @@
#define _ASM_X86_UNACCEPTED_MEMORY_H
#include <linux/efi.h>
+#include <asm/e820/api.h>
#include <asm/tdx.h>
#include <asm/sev.h>
-static inline void arch_accept_memory(phys_addr_t start, phys_addr_t end)
+static inline void __arch_accept_memory(phys_addr_t start, phys_addr_t end)
{
/* Platform-specific memory-acceptance call goes here */
if (cpu_feature_enabled(X86_FEATURE_TDX_GUEST)) {
@@ -18,6 +19,26 @@ static inline void arch_accept_memory(phys_addr_t start, phys_addr_t end)
}
}
+static inline void arch_accept_memory(phys_addr_t start, phys_addr_t end)
+{
+ u32 i;
+
+ for (i = 0; i < e820_table->nr_entries; i++) {
+ struct e820_entry *entry = &e820_table->entries[i];
+ phys_addr_t s, e;
+
+ if (entry->type != E820_TYPE_RAM)
+ continue;
+
+ s = max_t(phys_addr_t, start, entry->addr);
+ e = min_t(phys_addr_t, end, entry->addr + entry->size);
+ if (s >= e)
+ continue;
+
+ __arch_accept_memory(s, e);
+ }
+}
+
static inline struct efi_unaccepted_memory *efi_get_unaccepted_table(void)
{
if (efi.unaccepted == EFI_INVALID_TABLE_ADDR)
--
2.34.1
next reply other threads:[~2026-11-02 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 11:31 Pankaj Gupta [this message]
2026-11-02 11:41 ` Ard Biesheuvel
2026-11-02 11:51 ` Gupta, Pankaj
2026-11-02 12:01 ` Gupta, Pankaj
2026-11-02 12:11 ` 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=20261102113127.161823-1-pankaj.gupta@amd.com \
--to=pankaj.gupta@amd.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rppt@kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--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
all inboxes | Powered by JetHome®