From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Ni, Ray" <ray.ni@intel.com>, 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>
Subject: Re: managing memory attributes in PEI
Date: Tue, 23 May 2023 10:05:06 +0200 [thread overview]
Message-ID: <xc44en6lwmqjwqetcnrevphqggyuucm5ao3kvcrgxu4pgtfjnh@isdblz4qj3f6> (raw)
In-Reply-To: <2e04e9da-5b5a-9c00-76fe-c149538ddc80@redhat.com>
Hi,
> >> Before we enabled SMM for OVMF, we had never really used IA32X64 OVMF --
> >> SMM-less ACPI S3 resume had just worked fine with X64-only OVMF. IA32X64
> >> only proved a great platform option to fall back to, when we realized
> >> that on X64 OVMF, ACPI S3 resume wouldn't just seamlessly extend to SMM.
> >
> > I don't quite understand. So, what's the conclusion of IA32X64 OVMF? Keep it? Remove it?
>
> As long as edk2 (core modules) will continue supporting IA32X64 firmware
> platforms, I think keeping OVMF IA32X64 is useful, minimally as a test
> bed for those core modules / PCDs / boot paths.
Agree.
I'll go switch downstream SMM-enabled builds from OvmfPkgIa32X64.dsc to
OvmfPkgX64.dsc ASAP, so for virtualization use cases OvmfPkgIa32X64.dsc
will not be needed any more.
But it indeed makes sense to keep OvmfPkgIa32X64.dsc for testing and CI
purposes. So the question what the future of OvmfPkgIa32X64.dsc (and
OvmfPkgIa32.dsc) should be is is more a question of what the overall
edk2 plans for IA32 are.
take care,
Gerd
next prev parent reply other threads:[~2023-05-23 8:05 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
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 [this message]
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=xc44en6lwmqjwqetcnrevphqggyuucm5ao3kvcrgxu4pgtfjnh@isdblz4qj3f6 \
--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