public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, ray.ni@intel.com
Cc: "Andrew Fish" <afish@apple.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Liu, Zhiguang" <zhiguang.liu@intel.com>,
	"Rebecca Cran" <rebecca@bsdio.com>,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	"Marvin Häuser" <mhaeuser@posteo.de>
Subject: Re: [edk2-devel] [RFT PATCH v3 2/5] UefiCpuPkg/CpuExceptionHandlerLib: Use single SEC/PEI version
Date: Fri, 31 Mar 2023 12:12:51 +0200	[thread overview]
Message-ID: <CAMj1kXEyfuraFPn9y_gED4FAPbB2X+iTUQPXffjE=x8=zk=vWg@mail.gmail.com> (raw)
In-Reply-To: <MN6PR11MB8244E80CFE439F9E5C16EE738C8F9@MN6PR11MB8244.namprd11.prod.outlook.com>

On Fri, 31 Mar 2023 at 11:56, Ni, Ray <ray.ni@intel.com> wrote:
>
> Ard,
> Thanks for the detailed commit messages. That really helps me to understand why XCODE version
> was needed.
>
> However, I feel it would be great if you can "highlight" what are changed by this patch.
> The following is just an example. You can reword as you like.
>
> 1. Change for non-XCODE SecPeiCpuExceptionHandlerLib:
>    * Use SecPeiExceptionHandlerAsm.nasm (renamed from ExceptionHandlerAsm.nasm)
>    * Removed some unnecessary absolute references
>    * (32 IDT stubs are still in .text.)

Indeed

> 2. Change for XCODE SecPeiCpuExceptionHandlerLib:
>    * Use SecPeiExceptionHandlerAsm.nasm instead of Xcode5ExceptionHandlerAsm.nasm
>    * CET logic is not in SecPeiExceptionHandlerAsm.nasm (but aligns to non-XCODE lib instance)

No, this does not actually change in this patch. The CET logic does
not exist in the generic SecPei version either before or after this
patch.

Only the Xcode version is changed, because that version uses the same
as the Dxe/Smm version, which does have the CET code.

>    * Fixed a bug that does runtime fixup in TEXT section in SPI flash.
>    * Emitted the code carrying the absolute symbol references into the .data which XCODE or
>       LLD linkers allow.
>      Then fixup can be done by other build tools such as GenFv if the code runs in SPI flash,
>      or by PE coff loader if the code is loaded to memory.
>
> Again, thanks for the quick patches just because I asked some XCODE questions.
>

No problem. I'd like to get this fixed too for OVMF.

  reply	other threads:[~2023-03-31 10:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  9:14 [RFT PATCH v3 0/5] UefiCpuPkg, OvmfPkg: Simplify CpuExceptionHandlerLib Ard Biesheuvel
2023-03-31  9:14 ` [RFT PATCH v3 1/5] BaseTools/tools_def CLANGDWARF: Permit text relocations Ard Biesheuvel
2023-03-31  9:14 ` [RFT PATCH v3 2/5] UefiCpuPkg/CpuExceptionHandlerLib: Use single SEC/PEI version Ard Biesheuvel
2023-03-31  9:56   ` Ni, Ray
2023-03-31 10:12     ` Ard Biesheuvel [this message]
2023-03-31 10:19       ` [edk2-devel] " Ni, Ray
2023-03-31 10:49         ` Ard Biesheuvel
     [not found]   ` <17517877FE72B326.27612@groups.io>
2023-03-31  9:58     ` Ni, Ray
2023-03-31 10:14       ` Ard Biesheuvel
2023-03-31 10:16         ` Ni, Ray
2023-03-31 10:19           ` Ard Biesheuvel
2023-03-31  9:14 ` [RFT PATCH v3 3/5] UefiCpuPkg/CpuExceptionHandlerLib: Make runtime fixups XCODE-only Ard Biesheuvel
2023-03-31 10:03   ` [edk2-devel] " Ni, Ray
2023-03-31 10:20   ` Ni, Ray
2023-03-31  9:14 ` [RFT PATCH v3 4/5] OvmfPkg: Drop special Xcode5 version of exception handler library Ard Biesheuvel
2023-03-31  9:14 ` [RFT PATCH v3 5/5] UefiCpuPkg/CpuExceptionHandlerLib: Drop special XCODE5 version Ard Biesheuvel
2023-03-31 10:08 ` [edk2-devel] [RFT PATCH v3 0/5] UefiCpuPkg, OvmfPkg: Simplify CpuExceptionHandlerLib Ni, Ray
2023-03-31 10:15   ` Ard Biesheuvel
2023-03-31 10:41   ` Marvin Häuser
2023-03-31 11:03     ` Ard Biesheuvel
2023-03-31 11:09       ` Marvin Häuser
2023-03-31 14:39         ` Ni, Ray
2023-03-31 14:42           ` Marvin Häuser

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='CAMj1kXEyfuraFPn9y_gED4FAPbB2X+iTUQPXffjE=x8=zk=vWg@mail.gmail.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