From: "Dionna Glaze" <dionnaglaze@google.com>
To: devel@edk2.groups.io, robert@ami.com
Cc: "michael.d.kinney@intel.com" <michael.d.kinney@intel.com>,
"gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
"zhiguang.liu@intel.com" <zhiguang.liu@intel.com>,
"dandan.bi@intel.com" <dandan.bi@intel.com>
Subject: Re: [edk2-devel] [PATCH 2/2] MdeModulePkg: Added call to signal New Event
Date: Tue, 8 Nov 2022 15:42:19 -0800 [thread overview]
Message-ID: <CAAH4kHZRJjLeE=pRWOqAzbCR1ZjaGMFiOXX-nOaJq5OYA8sjUQ@mail.gmail.com> (raw)
In-Reply-To: <20221108202815.1487-3-robert@ami.com>
>
> This code signals the Before Exit Boot Services event at the beginning
> of the ExitBootServices() function. This gives all the rest of the
> code to prepare for the ExitBootServices event.
>
Hi Robert, I think we're both trying to do this at the same time. See
the patch series "SEV-SNP accepted memory and BeforeExitBootServices"
which suppose now is not appropriately titled since Michael asked me
to add the AfterReadyToBoot event.
--
-Dionna Glaze, PhD (she/her)
next prev parent reply other threads:[~2022-11-08 23:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 20:28 [edk2][PATCH 0/2] Add Events introduced in UEFI 2.9 Robert Phelps
2022-11-08 20:28 ` [PATCH 1/2] MdePkg: Add New Event Definitions from " Robert Phelps
2022-11-08 20:28 ` [PATCH 2/2] MdeModulePkg: Added call to signal New Event Robert Phelps
2022-11-08 23:42 ` Dionna Glaze [this message]
2022-11-09 15:49 ` [edk2-devel] " Robert Phelps
2022-11-09 16:21 ` Dionna Glaze
2022-11-09 16:52 ` Michael D Kinney
2022-11-09 16:58 ` Dionna Glaze
2022-11-09 17:31 ` Robert Phelps
2022-11-09 18:01 ` Dionna Glaze
2022-11-08 22:44 ` [edk2][PATCH 0/2] Add Events introduced in UEFI 2.9 Michael D Kinney
2022-11-09 16:10 ` [edk2-devel] " Robert Phelps
2022-12-07 1:08 ` 回复: " gaoliming
2022-12-14 17:49 ` Robert Phelps
2022-12-21 1:16 ` 回复: [edk2-devel] " gaoliming
2023-01-11 19:11 ` [edk2-devel] " Robert Phelps
2023-01-11 21:16 ` Michael D Kinney
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='CAAH4kHZRJjLeE=pRWOqAzbCR1ZjaGMFiOXX-nOaJq5OYA8sjUQ@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