From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [PATCH v9 0/4] Add safe unaccepted memory behavior To: Yao, Jiewen ,devel@edk2.groups.io From: dave.hansen@linux.intel.com X-Originating-Location: Portland, Oregon, US (50.39.107.205) X-Originating-Platform: Linux Chrome 108 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Fri, 13 Jan 2023 08:00:39 -0800 References: In-Reply-To: Message-ID: <16581.1673625639418051810@groups.io> Content-Type: multipart/alternative; boundary="dHfRQczY9iFBwHKnX4kA" --dHfRQczY9iFBwHKnX4kA Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Folks, My hope (from the x86 side at least) was that all functional Linux TDX gues= ts will have memory acceptance support.=C2=A0 We don't have fully-functiona= l guest code yet and assuming that Linux memory acceptance support will be = in place before we get there. Basically, I was hoping that Linux could get away without needing any kind = of negotiation with the firmware. (btw, I'm replying in the web interface.=C2=A0 Apologies for any odd format= ting) --dHfRQczY9iFBwHKnX4kA Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Folks,

My hope (from the x86 side at least) was that all func= tional Linux TDX guests will have memory acceptance support.  We don't= have fully-functional guest code yet and assuming that Linux memory accept= ance support will be in place before we get there.

Basically, I = was hoping that Linux could get away without needing any kind of negotiatio= n with the firmware.

(btw, I'm replying in the web interface.&nb= sp; Apologies for any odd formatting) --dHfRQczY9iFBwHKnX4kA--