From: Tom Lendacky <thomas.lendacky@amd.com>
To: coconut-svsm@lists.linux.dev,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>
Cc: Jon Lange <jlange@microsoft.com>,
"kraxel@redhat.com" <kraxel@redhat.com>,
"Relph, Richard" <Richard.Relph@amd.com>,
"Rodel, Jorg" <Joerg.Roedel@amd.com>,
Melody Wang <huibo.wang@amd.com>
Subject: SVSM draft specification (v1.01 draft #3)
Date: Fri, 3 Oct 2025 11:01:38 -0500 [thread overview]
Message-ID: <39cc8435-5643-4a16-8eb5-5e12f15566a1@amd.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Attached is the next version of the draft SVSM specification with the
following changes since the previous version:
- APIC emulation protocol added
- Coconut-SVSM will need to be audited, as the current APIC emulation
code does not completely match the "Alternate Injection Support"
specification on which this protocol is based.
- Reboot protocol added
- Core protocol v2 update:
- New flag to allow fallback from 2M to 4K during SVSM_CORE_PVALIDATE
when RMPADJUST/PVALIDATE return size mismatch
Please review. If there are no or only minor comments, this draft will
become the next version of the specification.
Thanks,
Tom
[-- Attachment #2: SVSM-Draft-v1.01.pdf --]
[-- Type: application/pdf, Size: 1039758 bytes --]
next reply other threads:[~2025-10-03 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 16:01 Tom Lendacky [this message]
2025-10-04 11:19 ` SVSM draft specification (v1.01 draft #3) Nicolai Stange
2025-10-06 14:44 ` Relph, Richard
2025-10-06 16:17 ` Nicolai Stange
2025-10-06 18:46 ` Relph, Richard
2025-10-06 17:56 ` Tom Lendacky
2025-10-07 2:20 ` [EXTERNAL] " Jon Lange
2025-10-07 2:59 ` James Bottomley
2025-10-07 14:37 ` Tom Lendacky
2025-10-07 18:52 ` Relph, Richard
2025-11-03 2:28 ` Melody Wang
2025-11-04 22:56 ` Melody Wang
[not found] ` <CY8PR12MB830036BA88DD5997A707ACAB95C2A@CY8PR12MB8300.namprd12.prod.outlook.com>
2025-11-06 3:40 ` Melody Wang
2025-11-07 21:55 ` [EXTERNAL] " Jon Lange
2025-11-12 17:52 ` Carlos López
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=39cc8435-5643-4a16-8eb5-5e12f15566a1@amd.com \
--to=thomas.lendacky@amd.com \
--cc=Joerg.Roedel@amd.com \
--cc=Richard.Relph@amd.com \
--cc=coconut-svsm@lists.linux.dev \
--cc=huibo.wang@amd.com \
--cc=jlange@microsoft.com \
--cc=kraxel@redhat.com \
--cc=linux-coco@lists.linux.dev \
/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