From: "Laszlo Ersek" <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, "Ni, Ray" <ray.ni@intel.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
edk2-devel-groups-io <devel@edk2.groups.io>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Taylor Beebe <t@taylorbeebe.com>,
Oliver Smith-Denny <osd@smith-denny.com>
Subject: Re: managing memory attributes in PEI
Date: Tue, 23 May 2023 07:46:09 +0200 [thread overview]
Message-ID: <34b9caa6-03e0-f565-805c-c9daecacc516@redhat.com> (raw)
In-Reply-To: <cw52a7ey27yg4ehf3kmpeufkmdim2lfez6fnovq3g4r4qrd4wc@vfhiv4wmmqgg>
On 5/23/23 06:49, Gerd Hoffmann wrote:
> On Mon, May 22, 2023 at 11:20:16PM +0000, Ni, Ray wrote:
>> Gerd,
>> The S3 path has been 64bit ready.
>> Can you check if OVMF pei64 image can do s3?
>>
>> At least internally in some real platform we tested s3 flow with 64bit PEI.
>
> Tested on OVMF, passed too.
>
> Which are the commits implementing this? I'd like the reference them in
> the commit message for S3Verification() removal.
commit 6acf72901a2e / bug 4195, AFAIK; there could be other related
commits since I last looked, of course
next prev parent reply other threads:[~2023-05-23 5:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 11:31 managing memory attributes in PEI Ard Biesheuvel
2023-05-22 12:06 ` Gerd Hoffmann
2023-05-22 23:20 ` Ni, Ray
2023-05-23 4:49 ` Gerd Hoffmann
2023-05-23 5:46 ` Laszlo Ersek [this message]
2023-05-23 5:50 ` [edk2-devel] " Ni, Ray
2023-05-23 5:44 ` Laszlo Ersek
2023-05-23 5:31 ` Laszlo Ersek
2023-05-23 5:39 ` Ni, Ray
2023-05-23 7:34 ` Laszlo Ersek
2023-05-23 7:52 ` Ni, Ray
2023-05-23 7:54 ` Ard Biesheuvel
2023-05-23 8:05 ` Gerd Hoffmann
2023-05-23 8:15 ` Ard Biesheuvel
2023-05-23 14:49 ` [edk2-devel] " Michael D Kinney
2023-05-23 14:58 ` Ard Biesheuvel
2023-05-23 15:14 ` Michael D Kinney
2023-05-23 15:51 ` Ard Biesheuvel
2023-05-23 16:47 ` Michael D Kinney
2023-05-24 2:54 ` Ni, Ray
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=34b9caa6-03e0-f565-805c-c9daecacc516@redhat.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