public inbox for linux-coco@lists.linux.dev
 help / color / mirror / Atom feed
From: Melody Wang <huibo.wang@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
	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>
Subject: Re: SVSM draft specification (v1.01 draft #3)
Date: Tue, 4 Nov 2025 14:56:11 -0800	[thread overview]
Message-ID: <466b9735-279d-4353-8ec7-8edc54c24986@amd.com> (raw)
In-Reply-To: <e1ff5baa-39d5-408b-afea-79cb398f0ac4@amd.com>

Hi Tom,

The Destination Format Register (DFR) is no longer needed and is not 
supported in X2APIC, so that answers my question.

The question still remains open is that whether LDR should be supported 
in the SVSM.

Thanks,
Melody

On 11/2/25 6:28 PM, Melody Wang wrote:
> Hi Tom,
> 
> In the section 9.1 SVSM_APIC_QUERY_FEATURES call,
> 
> "The APIC emulation supports the following APIC registers:"
> 
> The Destination Format Register (DFR) is also mentioned in the Alternate 
> Injection spec from Jon Lange.
> 
> However, the DFR and the LDR both are not implemented in the SVSM code 
> now, so the question is : should we remove the DFR and LDR from the spec 
> or should we implement these two registers in the SVSM?
> 
> On 10/3/25 9:01 AM, Tom Lendacky wrote:
>> 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
> 

-- 
Thanks,
Melody


  reply	other threads:[~2025-11-04 22:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 16:01 SVSM draft specification (v1.01 draft #3) Tom Lendacky
2025-10-04 11:19 ` 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 [this message]
     [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=466b9735-279d-4353-8ec7-8edc54c24986@amd.com \
    --to=huibo.wang@amd.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=Richard.Relph@amd.com \
    --cc=coconut-svsm@lists.linux.dev \
    --cc=jlange@microsoft.com \
    --cc=kraxel@redhat.com \
    --cc=linux-coco@lists.linux.dev \
    --cc=thomas.lendacky@amd.com \
    /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