From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124])
 by mx.groups.io with SMTP id smtpd.web11.14583.1684820777835004633
 for <devel@edk2.groups.io>;
 Mon, 22 May 2023 22:46:18 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=HMovMvPW;
 spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1684820777;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=FOB81L2NbZ0/uN0lxu0ig7nGaXVCbXLKz5JObP6EA9I=;
	b=HMovMvPWoAb1vjx+3biQopPxd72VDxb04TgYg7NhKJvXWJTVuF+X8yN5NxHqXMmR3NxsjR
	88h4h7cwSlQ8n/F0lvrPwmU3I3nCEyWoIlSUAQDXSYN1lSnOPrRTKbTYQ9T67k0UGYr4Cv
	zGu0EXqrnklDeLhEylglAiJBsFPr+Sw=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com
 [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-658-TWRju_VtPZqH80RUtIrkhA-1; Tue, 23 May 2023 01:46:13 -0400
X-MC-Unique: TWRju_VtPZqH80RUtIrkhA-1
Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 18E208032FA;
	Tue, 23 May 2023 05:46:13 +0000 (UTC)
Received: from [10.39.192.98] (unknown [10.39.192.98])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 6F55A492B00;
	Tue, 23 May 2023 05:46:11 +0000 (UTC)
Message-ID: <34b9caa6-03e0-f565-805c-c9daecacc516@redhat.com>
Date: Tue, 23 May 2023 07:46:09 +0200
MIME-Version: 1.0
Subject: Re: managing memory attributes in PEI
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>
References: <CAMj1kXHy22V86txgAvog49EjqGmU43MfTrLSMEphzFHhqrARng@mail.gmail.com>
 <rner7qwxzoccfrtcz3tihlx7qufjojzwjtz6wvh2l2nyj5krc3@mnejocmagezm>
 <MN6PR11MB8244511DC17E4F9569EED20D8C439@MN6PR11MB8244.namprd11.prod.outlook.com>
 <cw52a7ey27yg4ehf3kmpeufkmdim2lfez6fnovq3g4r4qrd4wc@vfhiv4wmmqgg>
From: "Laszlo Ersek" <lersek@redhat.com>
In-Reply-To: <cw52a7ey27yg4ehf3kmpeufkmdim2lfez6fnovq3g4r4qrd4wc@vfhiv4wmmqgg>
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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