public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Dionna Glaze" <dionnaglaze@google.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Ard Biesheuvel <ardb@kernel.org>,
	 Gerd Hoffman <kraxel@redhat.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 4/4] MdePkg: Signal AfterReadyToBoot after ReadyToBoot
Date: Wed, 9 Nov 2022 09:42:53 -0800	[thread overview]
Message-ID: <CAAH4kHYRP0Z1X-5Kv_3ofxBOvRFE1V2UyPnCWdADvA8A9U0fOw@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB49295B3BCC164F118FDE6230D23E9@CO1PR11MB4929.namprd11.prod.outlook.com>

Okay, so drop v2 and go back to review v1? Nothing changed other than this.

On Wed, Nov 9, 2022 at 9:35 AM Kinney, Michael D
<michael.d.kinney@intel.com> wrote:
>
> Hi Dionna,
>
> My mistake.  I misread the UEFI 2.9 Spec content and thought they were both for exit boot services.
>
> Your patch series with only Before Exit Boot Services is appropriate for your change.
>
> The After Ready To Boot can be in its own patch series.
>
> Best regards,
>
> Mike
>
> > -----Original Message-----
> > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Dionna Glaze via groups.io
> > Sent: Wednesday, November 9, 2022 9:12 AM
> > To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
> > Cc: Ard Biesheuvel <ardb@kernel.org>; Gerd Hoffman <kraxel@redhat.com>; Yao, Jiewen <jiewen.yao@intel.com>
> > Subject: Re: [edk2-devel] [PATCH v2 4/4] MdePkg: Signal AfterReadyToBoot after ReadyToBoot
> >
> > > I gave feedback about After Exit Boot Services event.
> > >
> >
> > I saw no such event in the specification
> >
> > > Why is an After Ready To Boot signal now part of this series?
> > >
> >
> > I thought that's the event you meant, since its mantis number is 2042,
> > whereas before exit boot services is 2043. That fits the "same time"
> > you mentioned in the other email.
> >
> >
> > --
> > -Dionna Glaze, PhD (she/her)
> >
> >
> > 
> >
>


-- 
-Dionna Glaze, PhD (she/her)

  reply	other threads:[~2022-11-09 17:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 21:15 [PATCH v2 0/4] SEV-SNP accepted memory and BeforeExitBootServices Dionna Glaze
2022-11-08 21:15 ` [PATCH v2 1/4] OvmfPkg: Realize EfiMemoryAcceptProtocol in AmdSevDxe Dionna Glaze
2022-11-08 21:15 ` [PATCH v2 2/4] MdePkg: Add event groups for boot events Dionna Glaze
2022-11-08 21:15 ` [PATCH v2 3/4] MdeModulePkg: Notify BeforeExitBootServices in CoreExitBootServices Dionna Glaze
2022-11-08 21:15 ` [PATCH v2 4/4] MdePkg: Signal AfterReadyToBoot after ReadyToBoot Dionna Glaze
2022-11-09 17:08   ` Michael D Kinney
2022-11-09 17:11     ` [edk2-devel] " Dionna Glaze
2022-11-09 17:31       ` Michael D Kinney
2022-11-09 17:42         ` Dionna Glaze [this message]
2022-12-07  1:26   ` 回复: " gaoliming
2022-12-07  5:27     ` 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=CAAH4kHYRP0Z1X-5Kv_3ofxBOvRFE1V2UyPnCWdADvA8A9U0fOw@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