From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: devel@edk2.groups.io, ardb@kernel.org
Cc: "Ni, Ray" <ray.ni@intel.com>, "Andrew Fish" <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
"Rebecca Cran" <rebecca@bsdio.com>,
"Marvin Häuser" <mhaeuser@posteo.de>
Subject: Re: [edk2-devel] [PATCH v4 0/6] UefiCpuPkg, OvmfPkg: Simplify CpuExceptionHandlerLib
Date: Mon, 3 Apr 2023 17:18:21 -0500 [thread overview]
Message-ID: <2f4c1b8b-0eec-2a78-b6ac-d64341e19427@amd.com> (raw)
In-Reply-To: <20230403142920.1921619-1-ardb@kernel.org>
On 4/3/23 09:29, Ard Biesheuvel via groups.io wrote:
> We have a special version of CpuExceptionHandlerLib for XCODE5, whose
> linker (LLD) does not permit absolute symbol references in read-only
> sections.
>
> Instead of fixing this up at runtime for all toolchains (which is done
> by writing the fixed up values to the .text section, which we'd prefer
> to avoid), tweak the SEC/PEI version so it does not need this, and
> update the remaining versions to only incorporate this logic when using
> the XCODE toolchain.
>
> Changes since v3:
> - Add another patch to move PeiCpuExceptionHandlerLib to SEC/PEI version
> of the NASM source file
> - Improve commit logs
>
> Changes since v2:
> - As Marvin points out, using '-read_only_relocs suppress' with the X64
> XCODE linker is a terrible idea, as it corrupts the resulting PE
> binaries, so instead, let's do the following:
> . tweak the SEC/PEI version of the library so the relocs are emitted
> into .data when using XCODE;
> . tweak the other versions so the runtime fixups are only done when
> using XCODE
> - add acks from Jiewen and Ray
>
> Changes since v1:
> - pass linker switches to permit absolute relocations in read-only
> regions, and keep all code in .text
>
> Cc: "Ni, Ray" <ray.ni@intel.com>
> Cc: Andrew Fish <afish@apple.com>
> Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
> Cc: "Liu, Zhiguang" <zhiguang.liu@intel.com>
> Cc: Rebecca Cran <rebecca@bsdio.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Cc: Marvin Häuser <mhaeuser@posteo.de>
Validated against SEV-ES (which was part of the original reason for the
split out) and SEV-SNP guests. Both guest types boot successfully.
Tested-by: Tom Lendacky <thomas.lendacky@amd.com>
>
> Ard Biesheuvel (6):
> BaseTools/tools_def CLANGDWARF: Permit text relocations
> UefiCpuPkg/CpuExceptionHandlerLib: Use single SEC/PEI version
> UefiCpuPkg/PeiCpuExceptionHandlerLib: Use SEC/PEI specific asm
> component
> UefiCpuPkg/CpuExceptionHandlerLib: Make runtime fixups XCODE-only
> OvmfPkg: Drop special Xcode5 version of exception handler library
> UefiCpuPkg/CpuExceptionHandlerLib: Drop special XCODE5 version
>
> BaseTools/Conf/tools_def.template | 2 +-
> OvmfPkg/AmdSev/AmdSevX64.dsc | 4 -
> OvmfPkg/CloudHv/CloudHvX64.dsc | 4 -
> OvmfPkg/IntelTdx/IntelTdxX64.dsc | 4 -
> OvmfPkg/Microvm/MicrovmX64.dsc | 4 -
> OvmfPkg/OvmfPkgIa32.dsc | 4 -
> OvmfPkg/OvmfPkgIa32X64.dsc | 4 -
> OvmfPkg/OvmfPkgX64.dsc | 4 -
> OvmfPkg/OvmfXen.dsc | 4 -
> UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib.inf | 5 +-
> UefiCpuPkg/Library/CpuExceptionHandlerLib/PeiCpuExceptionHandlerLib.inf | 4 +-
> UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib.inf | 4 +-
> UefiCpuPkg/Library/CpuExceptionHandlerLib/SmmCpuExceptionHandlerLib.inf | 4 +-
> UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.nasm | 116 +++++++++++++++++---
> UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/{Xcode5ExceptionHandlerAsm.nasm => SecPeiExceptionHandlerAsm.nasm} | 108 +++---------------
> UefiCpuPkg/Library/CpuExceptionHandlerLib/Xcode5SecPeiCpuExceptionHandlerLib.inf | 65 -----------
> UefiCpuPkg/Library/CpuExceptionHandlerLib/Xcode5SecPeiCpuExceptionHandlerLib.uni | 18 ---
> UefiCpuPkg/UefiCpuPkg.dsc | 7 --
> 18 files changed, 133 insertions(+), 232 deletions(-)
> rename UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/{Xcode5ExceptionHandlerAsm.nasm => SecPeiExceptionHandlerAsm.nasm} (70%)
> delete mode 100644 UefiCpuPkg/Library/CpuExceptionHandlerLib/Xcode5SecPeiCpuExceptionHandlerLib.inf
> delete mode 100644 UefiCpuPkg/Library/CpuExceptionHandlerLib/Xcode5SecPeiCpuExceptionHandlerLib.uni
>
next prev parent reply other threads:[~2023-04-03 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 14:29 [PATCH v4 0/6] UefiCpuPkg, OvmfPkg: Simplify CpuExceptionHandlerLib Ard Biesheuvel
2023-04-03 14:29 ` [PATCH v4 1/6] BaseTools/tools_def CLANGDWARF: Permit text relocations Ard Biesheuvel
2023-04-05 17:11 ` Rebecca Cran
2023-04-03 14:29 ` [PATCH v4 2/6] UefiCpuPkg/CpuExceptionHandlerLib: Use single SEC/PEI version Ard Biesheuvel
2023-04-06 5:54 ` Ni, Ray
2023-04-03 14:29 ` [PATCH v4 3/6] UefiCpuPkg/PeiCpuExceptionHandlerLib: Use SEC/PEI specific asm component Ard Biesheuvel
2023-04-06 6:00 ` Ni, Ray
2023-04-03 14:29 ` [PATCH v4 4/6] UefiCpuPkg/CpuExceptionHandlerLib: Make runtime fixups XCODE-only Ard Biesheuvel
2023-04-03 14:29 ` [PATCH v4 5/6] OvmfPkg: Drop special Xcode5 version of exception handler library Ard Biesheuvel
2023-04-03 14:29 ` [PATCH v4 6/6] UefiCpuPkg/CpuExceptionHandlerLib: Drop special XCODE5 version Ard Biesheuvel
2023-04-03 22:18 ` Lendacky, Thomas [this message]
2023-04-04 7:57 ` [PATCH v4 0/6] UefiCpuPkg, OvmfPkg: Simplify CpuExceptionHandlerLib Marvin Häuser
2023-04-04 9:46 ` [edk2-devel] " Ard Biesheuvel
2023-04-05 17:11 ` Rebecca Cran
2023-04-06 6:55 ` 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=2f4c1b8b-0eec-2a78-b6ac-d64341e19427@amd.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