From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Wu, Jiaxin" <jiaxin.wu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Ni, Ray" <ray.ni@intel.com>, "Zeng, Star" <star.zeng@intel.com>,
"Kumar, Rahul R" <rahul.r.kumar@intel.com>,
"Dong, Guo" <guo.dong@intel.com>,
"Rhodes, Sean" <sean@starlabs.systems>,
"Lu, James" <james.lu@intel.com>, "Guo, Gua" <gua.guo@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Abdul Lateef Attar <AbdulLateef.Attar@amd.com>,
Abner Chang <abner.chang@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH v3 00/13] Add SmmRelocationLib
Date: Wed, 24 Apr 2024 13:29:11 +0200 [thread overview]
Message-ID: <4p5no7tieltk7n2p4mzkuy2ypd2kkxdwxs6lsfnwlrlucosmba@zs5cfcjhfz5y> (raw)
In-Reply-To: <MN0PR11MB6158A5AB114B2E4736A3F4C8FE102@MN0PR11MB6158.namprd11.prod.outlook.com>
On Wed, Apr 24, 2024 at 03:56:56AM +0000, Wu, Jiaxin wrote:
> Hi Gerd,
>
> AMD version is not work for IA32X64 ovmf.
>
> I checked the detailed: CpuSaveState->x64 is always used for OVMF no matter IA32 or X64, while AMD is not, which is decided by the MSR EFER_ADDRESS LMA bit check.
Hmm, probably because only PEI runs in 32-bit mode whereas DXE and SMM
run in 64-bit mode, so 32-bit PEI has to prepare things for the 64-bit
SMM.
> There is a potential issue/open in OVMF why need use the X64
> CpuSaveState for IA32. Before this open resolved, I still prefer to
> keep use the ovmf specific lib instance.
Yes, lets stick to the ovmf version for now, and maybe remove it later
when fixing the ia32 ovmf builds.
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118204): https://edk2.groups.io/g/devel/message/118204
Mute This Topic: https://groups.io/mt/105593568/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-04-24 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17C74D78B0B952AD.15491@groups.io>
2024-04-18 8:02 ` [edk2-devel] [PATCH v3 00/13] Add SmmRelocationLib Wu, Jiaxin
2024-04-22 7:57 ` Gerd Hoffmann
2024-04-23 7:31 ` Wu, Jiaxin
2024-04-23 8:43 ` Gerd Hoffmann
2024-04-23 12:16 ` Wu, Jiaxin
2024-04-24 3:56 ` Wu, Jiaxin
2024-04-24 11:29 ` Gerd Hoffmann [this message]
2024-04-25 0:54 ` Wu, Jiaxin
2024-04-25 5:50 ` Ni, Ray
2024-04-25 6:58 ` Gerd Hoffmann
2024-04-26 6:07 ` Ni, Ray
2024-04-26 13:18 ` Lendacky, Thomas via groups.io
2024-04-18 8:03 ` Wu, Jiaxin
2024-04-19 3:35 ` Ni, Ray
2024-04-19 3:47 ` Chang, Abner via groups.io
2024-04-19 3:55 ` Wu, Jiaxin
2024-04-18 6:55 Wu, Jiaxin
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=4p5no7tieltk7n2p4mzkuy2ypd2kkxdwxs6lsfnwlrlucosmba@zs5cfcjhfz5y \
--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