From: Borislav Petkov <bp@kernel.org>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: <linux-coco@lists.linux.dev>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: [PATCH 0/3] x86/sev: Carve out the SVSM support code
Date: Thu, 4 Dec 2025 13:48:05 +0100 [thread overview]
Message-ID: <20251204124809.31783-1-bp@kernel.org> (raw)
From: "Borislav Petkov (AMD)" <bp@alien8.de>
Hi,
I've been meaning to do this for a while now but didn't have a good idea how
to do it nicely. Using the internal header makes it almost trivial.
Thx.
Borislav Petkov (AMD) (3):
x86/sev: Move the internal header
x86/sev: Add internal header guards
x86/sev: Carve out the SVSM code into a separate compilation unit
arch/x86/boot/startup/sev-startup.c | 3 +-
arch/x86/coco/sev/Makefile | 2 +-
arch/x86/coco/sev/core.c | 380 +-----------------
.../sev-internal.h => coco/sev/internal.h} | 32 ++
arch/x86/coco/sev/noinstr.c | 3 +-
arch/x86/coco/sev/svsm.c | 362 +++++++++++++++++
arch/x86/coco/sev/vc-handle.c | 3 +-
7 files changed, 403 insertions(+), 382 deletions(-)
rename arch/x86/{include/asm/sev-internal.h => coco/sev/internal.h} (75%)
create mode 100644 arch/x86/coco/sev/svsm.c
--
2.51.0
next reply other threads:[~2025-12-04 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 12:48 Borislav Petkov [this message]
2025-12-04 12:48 ` [PATCH 1/3] x86/sev: Move the internal header Borislav Petkov
2025-12-04 14:18 ` Tom Lendacky
2025-12-04 14:57 ` Borislav Petkov
2025-12-04 12:48 ` [PATCH 2/3] x86/sev: Add internal header guards Borislav Petkov
2025-12-31 12:25 ` [tip: x86/sev] " tip-bot2 for Borislav Petkov (AMD)
2025-12-04 12:48 ` [PATCH 3/3] x86/sev: Carve out the SVSM code into a separate compilation unit Borislav Petkov
2025-12-31 12:25 ` [tip: x86/sev] " tip-bot2 for Borislav Petkov (AMD)
2025-12-04 14:53 ` [PATCH 0/3] x86/sev: Carve out the SVSM support code Tom Lendacky
2025-12-04 15:06 ` Borislav Petkov
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=20251204124809.31783-1-bp@kernel.org \
--to=bp@kernel.org \
--cc=bp@alien8.de \
--cc=linux-coco@lists.linux.dev \
--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.