public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"dionnaglaze@google.com" <dionnaglaze@google.com>
Cc: Ard Biescheuvel <ardb@kernel.org>,
	"Xu, Min M" <min.m.xu@intel.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	James Bottomley <jejb@linux.ibm.com>,
	"Tom Lendacky" <Thomas.Lendacky@amd.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	Andrew Fish <afish@apple.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v7 0/7] Add safe unaccepted memory behavior
Date: Fri, 14 Oct 2022 06:20:30 +0000	[thread overview]
Message-ID: <MWHPR11MB1631D7576710A4F755BDFC478C249@MWHPR11MB1631.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221005203329.469866-1-dionnaglaze@google.com>

> 
> To allow the OS loader to prevent the eager acceptance, we add a new
> protocol, up for standardization, AcceptAllUnacceptedMemoryProtocol.
> This protocol has one interface, Disable(). The OS loader can inform the
> UEFI that it supports the unaccepted memory type and accepts the
> responsibility to accept it.
> 
> All images that support unaccepted memory must now locate and call this
> new BZ3987_ACCEPT_ALL_UNACCEPTED_MEMORY_PROTOCOL and call the Disable
> function.
> 

Can OsIndicationsSupported UEFI variable provide the similar functionality?


  parent reply	other threads:[~2022-10-14  6:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 20:33 [PATCH v7 0/7] Add safe unaccepted memory behavior Dionna Glaze
2022-10-05 20:33 ` [PATCH v7 1/7] OvmfPkg: Realize EfiMemoryAcceptProtocol in AmdSevDxe Dionna Glaze
2022-10-05 20:43   ` Lendacky, Thomas
2022-10-05 20:33 ` [PATCH v7 2/7] MdePkg: Add EFI_EVENT_BEFORE_EXIT_BOOT_SERVICES_GUID Dionna Glaze
2022-10-06 12:45   ` Ard Biesheuvel
2022-10-10  1:33     ` 回复: [edk2-devel] " gaoliming
2022-10-05 20:33 ` [PATCH v7 3/7] MdeModulePkg: Notify BeforeExitBootServices in CoreExitBootServices Dionna Glaze
2022-10-05 20:50   ` Lendacky, Thomas
2022-10-05 20:58     ` Dionna Glaze
2022-10-10  1:32       ` 回复: [edk2-devel] " gaoliming
     [not found]     ` <171B47E3227F0BCA.23411@groups.io>
2022-10-05 21:01       ` Dionna Glaze
2022-10-06 12:46   ` Ard Biesheuvel
2022-10-05 20:33 ` [PATCH v7 4/7] OvmfPkg: Introduce CocoDxe driver Dionna Glaze
2022-10-05 20:33 ` [PATCH v7 5/7] MdePkg: Introduce the AcceptAllUnacceptedMemory protocol Dionna Glaze
2022-10-05 20:33 ` [PATCH v7 6/7] OvmfPkg: Implement AcceptAllUnacceptedMemory in CocoDxe Dionna Glaze
2022-10-05 20:33 ` [PATCH v7 7/7] OvmfPkg/PlatformPei: SEV-SNP make >=4GB unaccepted Dionna Glaze
2022-10-05 21:02   ` Lendacky, Thomas
2022-10-14  6:20 ` Ni, Ray [this message]
2022-10-14 21:29   ` [edk2-devel] [PATCH v7 0/7] Add safe unaccepted memory behavior Dionna Glaze
2022-10-19  8:57     ` Ard Biesheuvel
2022-10-20 22:37       ` Dionna Glaze
2022-10-21 13:17         ` Ard Biesheuvel
2022-10-21 15:42           ` Dionna Glaze
2022-10-24  8:34 ` aik
2022-10-24 15:24   ` Dionna Glaze
2022-10-26  0:23     ` aik
2022-10-26  1:07       ` Dionna Glaze
2022-10-26  1:35         ` Alexey Kardashevskiy
2022-10-26  2:49           ` Alexey Kardashevskiy
2022-10-27  3:18             ` Alexey Kardashevskiy
2022-10-27 15:38               ` Dionna Glaze

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=MWHPR11MB1631D7576710A4F755BDFC478C249@MWHPR11MB1631.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