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
Date: Mon, 22 May 2023 14:06:46 +0200 [thread overview]
Message-ID: <rner7qwxzoccfrtcz3tihlx7qufjojzwjtz6wvh2l2nyj5krc3@mnejocmagezm> (raw)
In-Reply-To: <CAMj1kXHy22V86txgAvog49EjqGmU43MfTrLSMEphzFHhqrARng@mail.gmail.com>
> 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
next prev parent reply other threads:[~2023-05-22 12:06 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 [this message]
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
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=rner7qwxzoccfrtcz3tihlx7qufjojzwjtz6wvh2l2nyj5krc3@mnejocmagezm \
--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