public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Min Xu" <min.m.xu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>
Cc: "Gao, Zhichao" <zhichao.gao@intel.com>,
	"Ni, Ray" <ray.ni@intel.com>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	'Gerd Hoffmann' <kraxel@redhat.com>,
	'James Bottomley' <jejb@linux.ibm.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	'Tom Lendacky' <thomas.lendacky@amd.com>,
	"Gao, Jiaqi" <jiaqi.gao@intel.com>,
	"Wang, Jian J" <jian.j.wang@intel.com>,
	"Liu, Zhiguang" <zhiguang.liu@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] 回复: [PATCH V4 00/10] Introduce Lazy-accept for Tdx guest
Date: Tue, 18 Oct 2022 01:13:04 +0000	[thread overview]
Message-ID: <PH0PR11MB5064D3074963121EC3EAF426C5289@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <01f901d8dc4f$e9beeac0$bd3cc040$@byosoft.com.cn>

On October 10, 2022 10:28 AM, Gao Liming wrote:
> 
> Min:
>   I have no comments for new unaccepted resource type and unaccepted gcd
> type. In fact, they are mapping to UEFI EfiUnacceptedMemoryType.
> 
>   For new protocol EfiMemoryAcceptProtocol, I see another patch serial
> https://edk2.groups.io/g/devel/message/94763 base on it to introduce
> ACCEPT_ALL_UNACCEPTED_MEMORY_PROTOCOL. Can these two protocols
> be combined into one?
> 
HI, Liming
There are below discussions about your comments.
https://edk2.groups.io/g/devel/message/94869
https://edk2.groups.io/g/devel/message/94944
https://edk2.groups.io/g/devel/message/95050
https://edk2.groups.io/g/devel/message/95109

Do you think these discussions address your comments?

Thanks
Min

  parent reply	other threads:[~2022-10-18  1:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  0:02 [PATCH V4 00/10] Introduce Lazy-accept for Tdx guest Min Xu
2022-09-13  0:02 ` [PATCH V4 01/10] MdeModulePkg: Add PrePiHob.h Min Xu
2022-09-13  0:02 ` [PATCH V4 02/10] MdePkg: Increase EFI_RESOURCE_MAX_MEMORY_TYPE Min Xu
2022-09-21  8:10   ` Gerd Hoffmann
2022-09-13  0:02 ` [PATCH V4 03/10] OvmfPkg: Use BZ3937_EFI_RESOURCE_MEMORY_UNACCEPTED defined in MdeModulePkg Min Xu
2022-09-13  0:02 ` [PATCH V4 04/10] MdePkg: Add UEFI Unaccepted memory definition Min Xu
2022-09-13  0:02 ` [PATCH V4 05/10] MdeModulePkg: Update Dxe to handle unaccepted memory type Min Xu
2022-09-13  0:02 ` [PATCH V4 06/10] ShellPkg: Update shell command memmap to show unaccepted memory Min Xu
2022-09-13  0:02 ` [PATCH V4 07/10] OvmfPkg: Introduce lazy accept in PlatformInitLib and PlatformPei Min Xu
2022-09-21  8:11   ` Gerd Hoffmann
2022-09-13  0:02 ` [PATCH V4 08/10] MdePkg: The prototype definition of EdkiiMemoryAcceptProtocol Min Xu
2022-09-13  0:02 ` [PATCH V4 09/10] OvmfPkg: Realize EdkiiMemoryAcceptProtocol in TdxDxe Min Xu
2022-09-13  0:02 ` [PATCH V4 10/10] OvmfPkg: Call gEdkiiMemoryAcceptProtocolGuid to accept pages Min Xu
2022-09-22  5:25 ` [PATCH V4 00/10] Introduce Lazy-accept for Tdx guest Min Xu
2022-09-29  6:56   ` Min Xu
2022-10-10  2:27     ` 回复: " gaoliming
2022-10-10  3:08       ` [edk2-devel] " Min Xu
2022-10-10  3:18         ` Ni, Ray
2022-10-10 15:50           ` Dionna Glaze
2022-10-12  5:29             ` Min Xu
2022-10-13  5:27               ` Dionna Glaze
2022-10-18  1:13       ` Min Xu [this message]
2022-10-19  1:17         ` 回复: " gaoliming
2022-10-19  2:02           ` Min Xu
2022-10-21 15:58             ` Dionna Glaze
2022-10-25  1:07               ` Min Xu
2022-10-26  1:27                 ` 回复: " gaoliming
2022-10-26 13:35                   ` Min Xu
2022-11-01  1:18                     ` 回复: " gaoliming

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-list 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=PH0PR11MB5064D3074963121EC3EAF426C5289@PH0PR11MB5064.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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