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.13937.1684817375005998942
 for <devel@edk2.groups.io>;
 Mon, 22 May 2023 21:49:35 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TWHI7sYD;
 spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1684817374;
	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:
	 in-reply-to:in-reply-to:references:references;
	bh=nwEIAQLO2CEBTXKdmxIMSm1B9x8EuS/dBW3PfKY0Bc0=;
	b=TWHI7sYDTI6YfaOHip0k9qRM7hwgKsFAU5He2JxNxgNoepwfheuDhQWgbPxwRT+aYe9XzF
	wiiAAK41iCSSTP9YuV9aDkPwbSTNGobpcJExEk6SK4oOg8HkHXHbStUo7t3Ls6h4rnt90o
	ltuMbZ7+Lh7keQhAnMT49+Bm3BO1cC4=
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-208-uVSHh6ZVMPSqpXOQ0_U9pw-1; Tue, 23 May 2023 00:49:30 -0400
X-MC-Unique: uVSHh6ZVMPSqpXOQ0_U9pw-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 33BE9811E7F;
	Tue, 23 May 2023 04:49:30 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.37])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id DB4BC1121314;
	Tue, 23 May 2023 04:49:29 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 598661800626; Tue, 23 May 2023 06:49:28 +0200 (CEST)
Date: Tue, 23 May 2023 06:49:28 +0200
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "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>, 
	Laszlo Ersek <lersek@redhat.com>, Taylor Beebe <t@taylorbeebe.com>, 
	Oliver Smith-Denny <osd@smith-denny.com>
Subject: Re: managing memory attributes in PEI
Message-ID: <cw52a7ey27yg4ehf3kmpeufkmdim2lfez6fnovq3g4r4qrd4wc@vfhiv4wmmqgg>
References: <CAMj1kXHy22V86txgAvog49EjqGmU43MfTrLSMEphzFHhqrARng@mail.gmail.com>
 <rner7qwxzoccfrtcz3tihlx7qufjojzwjtz6wvh2l2nyj5krc3@mnejocmagezm>
 <MN6PR11MB8244511DC17E4F9569EED20D8C439@MN6PR11MB8244.namprd11.prod.outlook.com>
MIME-Version: 1.0
In-Reply-To: <MN6PR11MB8244511DC17E4F9569EED20D8C439@MN6PR11MB8244.namprd11.prod.outlook.com>
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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.

thanks,
  Gerd