From: "Dionna Glaze" <dionnaglaze@google.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: devel@edk2.groups.io, "Ni, Ray" <ray.ni@intel.com>,
"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, 21 Oct 2022 08:42:52 -0700 [thread overview]
Message-ID: <CAAH4kHbUoF2a+55Bc_=cfcwpwAmoYvdLH75ZvzrK26wJKEdH_w@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXFpadyExC_zM9CU7b6CWN17O7PQC8eN17Cqhwz2BA4moQ@mail.gmail.com>
> > I suppose that's true. Would you prefer volatile versions of
> > OsIndications/OsIndicationsSupported added to the spec, or this
> > proposed one-off toggle protocol? No specified global variables seem
> > overloadable with this duty.
> >
>
> No it would have to be a completely separate variable, I don't think
> we can use OsIndications for this.
Certainly, I meant new variables that are volatile and also play a
similar role as OsIndications[Supported].
--
-Dionna Glaze, PhD (she/her)
next prev parent reply other threads:[~2022-10-21 15:43 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 ` [edk2-devel] [PATCH v7 0/7] Add safe unaccepted memory behavior Ni, Ray
2022-10-14 21:29 ` 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 [this message]
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='CAAH4kHbUoF2a+55Bc_=cfcwpwAmoYvdLH75ZvzrK26wJKEdH_w@mail.gmail.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