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.20068.1684757213864301891
 for <devel@edk2.groups.io>;
 Mon, 22 May 2023 05:06:54 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=HnKpU+Kb;
 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=1684757212;
	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=5sQA4dkmYo1f/Idf3j6ZDlPq2ZOYegl4Obm6Ys299Ew=;
	b=HnKpU+Kb6bWoA4TPyXG1fupfY/t4JaC29nnLiEbrlW9BwpbAJUvG4H2FeYQkvjj5rO0+6+
	1+/yngH3fQxjj2MObxID+iXt3vE1VlK+58L37xrsQnjKpT0jF4LB8TZnpU3C4HQG6JNyxL
	kSA9r+Qkp270A8U06mf0jkAIcgN8R8Y=
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-636-xIGjr7AzN9OD0tj2J_EfRg-1; Mon, 22 May 2023 08:06:48 -0400
X-MC-Unique: xIGjr7AzN9OD0tj2J_EfRg-1
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 97182185A78F;
	Mon, 22 May 2023 12:06:47 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.139])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 577822166B25;
	Mon, 22 May 2023 12:06:47 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 25C361800606; Mon, 22 May 2023 14:06:46 +0200 (CEST)
Date: Mon, 22 May 2023 14:06:46 +0200
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>, Ray Ni <ray.ni@intel.com>, 
	Jiewen Yao <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: <rner7qwxzoccfrtcz3tihlx7qufjojzwjtz6wvh2l2nyj5krc3@mnejocmagezm>
References: <CAMj1kXHy22V86txgAvog49EjqGmU43MfTrLSMEphzFHhqrARng@mail.gmail.com>
MIME-Version: 1.0
In-Reply-To: <CAMj1kXHy22V86txgAvog49EjqGmU43MfTrLSMEphzFHhqrARng@mail.gmail.com>
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> So my questions are:
> - do we need to retain mixed IA32 / X64 support, and if so, why? (I
> think it is related to SMM emulation but I need someone to confirm
> this)

Yes, it's SMM related.  S3 suspend in SMM-enabled builds requires
32bit PEI.

Intel seems to be working on removing the IA32 dependency, by adding
full X64 support to various places in the code base.  There have been
numerous patch sets on the list over the last months, some of them
are merged meanwhile.  As far I know the patch series addressing the
suspend problem is not yet merged (Ray, Jiewen, please correct me if
I'm wrong).

So, right now we still need that, but I expect that to change in near
future.

take care,
  Gerd