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>,
Tom Lendacky <thomas.lendacky@amd.com>,
Borislav Petkov <bp@alien8.de>
Subject: [PATCH v4 0/3] efi: Don't initalize SEV-SNP from the EFI stub
Date: Tue, 9 Sep 2025 10:06:32 +0200 [thread overview]
Message-ID: <20250909080631.2867579-5-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
The EFI stub no longer invokes the legacy decompressor, and so there is
no longer any reason to perform all SEV-SNP initialization twice: it is
sufficient to rely on the SEV-SNP work done by the core kernel.
Changes since v3: [2]
- Drop patches that have been merged in the meantime
- Rebase onto tip/x86/sev
Note that the issue pointed out by Tom in reply to the v3 cover letter
has been fixed in the meantime as well [3]
Changes since v2: [1]
- rebase onto tip/x86/boot
- add patch to remove unused static inline fallback implementation of
sev_enable()
Changes since v1: [0]
- address shortcomings pointed out by Tom, related to missing checks and
to discovery of the CC blob table from the EFI stub
[0] https://lore.kernel.org/all/20250414130417.1486395-2-ardb+git@google.com/T/#u
[1] https://lore.kernel.org/all/20250416165743.4080995-6-ardb+git@google.com/T/#u
[2] https://lore.kernel.org/all/20250422100728.208479-7-ardb+git@google.com/T/#u
[3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8ed12ab1319b2d8e4a529504777aacacf71371e4
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Borislav Petkov <bp@alien8.de>
Ard Biesheuvel (3):
x86/boot: Drop unused sev_enable() fallback
x86/efistub: Obtain SEV CC blob address from the stub
x86/efistub: Don't bother enabling SEV in the EFI stub
arch/x86/boot/compressed/misc.h | 11 --------
arch/x86/include/asm/sev.h | 2 --
drivers/firmware/efi/libstub/x86-stub.c | 27 ++++++++++++--------
3 files changed, 16 insertions(+), 24 deletions(-)
base-commit: 0ca77f8d33e8136b8926775380506f78a8d04811
--
2.51.0.384.g4c02a37b29-goog
next reply other threads:[~2025-09-09 8:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 8:06 Ard Biesheuvel [this message]
2025-09-09 8:06 ` [PATCH v4 1/3] x86/boot: Drop unused sev_enable() fallback Ard Biesheuvel
2025-09-11 21:35 ` Tom Lendacky
2025-11-20 20:26 ` [tip: x86/sev] " tip-bot2 for Ard Biesheuvel
2025-09-09 8:06 ` [PATCH v4 2/3] x86/efistub: Obtain SEV CC blob address from the stub Ard Biesheuvel
2025-09-11 21:27 ` Tom Lendacky
2025-09-11 21:49 ` Ard Biesheuvel
2025-09-09 8:06 ` [PATCH v4 3/3] x86/efistub: Don't bother enabling SEV in the EFI stub Ard Biesheuvel
2025-09-11 21:53 ` Tom Lendacky
2025-09-12 7:29 ` Ard Biesheuvel
2025-09-12 8:26 ` Ard Biesheuvel
2025-09-12 13:32 ` Tom Lendacky
2025-09-15 16:08 ` Borislav Petkov
2025-09-12 20:34 ` Ashish Kalra
2025-09-12 22:22 ` 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=20250909080631.2867579-5-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.