public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, 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>,
	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:44:31 +0200	[thread overview]
Message-ID: <3d682c21-f7f1-8e23-b5a5-92e3fa51dd39@redhat.com> (raw)
In-Reply-To: <rner7qwxzoccfrtcz3tihlx7qufjojzwjtz6wvh2l2nyj5krc3@mnejocmagezm>

On 5/22/23 14:06, Gerd Hoffmann wrote:
>> 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).

You've forgotten about our discussion in <https://bugzilla.tianocore.org/show_bug.cgi?id=4195> :)

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

BTW just last evening I found out about X86-S:

- https://www.phoronix.com/news/Intel-X86-S-64-bit-Only
- https://www.intel.com/content/www/us/en/developer/articles/technical/envisioning-future-simplified-architecture.html
- https://cdrdv2.intel.com/v1/dl/getContent/776648

I'm slightly curious if those IA32->X64 "replacement" patches you mention are related to X86-S ;)

Laszlo


  parent reply	other threads:[~2023-05-23  5:44 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
2023-05-23  5:50         ` [edk2-devel] " Ni, Ray
2023-05-23  5:44   ` Laszlo Ersek [this message]
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=3d682c21-f7f1-8e23-b5a5-92e3fa51dd39@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