public inbox for linux-coco@lists.linux.dev
 help / color / mirror / Atom feed
From: Melody Wang <huibo.wang@amd.com>
To: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
	"coconut-svsm@lists.linux.dev" <coconut-svsm@lists.linux.dev>,
	"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
	Jon Lange <jlange@microsoft.com>
Cc: "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: Wed, 5 Nov 2025 19:40:20 -0800	[thread overview]
Message-ID: <79f2ac24-c716-4dcc-aa56-288a2539013e@amd.com> (raw)
In-Reply-To: <CY8PR12MB830036BA88DD5997A707ACAB95C2A@CY8PR12MB8300.namprd12.prod.outlook.com>

Sorry the last email was not sent to the mailing list, resend this email 
to fix it.

Hi Jon,

As mentioned in my previous two emails, the DFR is no longer needed and 
isn’t supported in X2APIC. Should we remove the DFR from the Alternate 
Injection spec?

Also, the LDR isn’t currently implemented in the SVSM. Should we plan to 
add it, or remove it from the spec as well?

Thanks,
Melody

On 11/5/25 5:07 PM, Wang, Huibo wrote:
> 
> Hi Jon,
> 
> As mentioned in my previous two emails, the *DFR* is no longer needed 
> and isn’t supported in *X2APIC*. Should we remove the DFR from the 
> *Alternate Injection* spec?
> Also, the *LDR* isn’t currently implemented in the *SVSM*. Should we 
> plan to add it, or remove it from the spec as well?
> Thanks,
> Melody

-- 
Thanks,
Melody


  parent reply	other threads:[~2025-11-06  3:40 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
     [not found]     ` <CY8PR12MB830036BA88DD5997A707ACAB95C2A@CY8PR12MB8300.namprd12.prod.outlook.com>
2025-11-06  3:40       ` Melody Wang [this message]
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=79f2ac24-c716-4dcc-aa56-288a2539013e@amd.com \
    --to=huibo.wang@amd.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=Richard.Relph@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=coconut-svsm@lists.linux.dev \
    --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