summaryrefslogtreecommitdiffstats
path: root/OvmfPkg
diff options
context:
space:
mode:
authorOliver Smith-Denny <osde@microsoft.com>2024-10-27 08:52:42 -0700
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2024-11-13 21:01:46 +0000
commitf0390f7bf14c1f5fe1205dc12185896150c70756 (patch)
tree3c8281827bef7e563aa2786b8a6bce62bcc1d472 /OvmfPkg
parent0c56edacfb727173cb5e4ed3a769ce28d3f40092 (diff)
downloadedk2-f0390f7bf14c1f5fe1205dc12185896150c70756.tar.gz
edk2-f0390f7bf14c1f5fe1205dc12185896150c70756.tar.bz2
edk2-f0390f7bf14c1f5fe1205dc12185896150c70756.zip
UefiCpuPkg: Make the ResetVector USER_DEFINED
The x86 reset vector is the initial FW code to run on an AP. It should not link to any libraries and is implemented entirely in assembly. This module is currently labled as SEC, because it runs during the SEC phase, but by having it SEC, it will be linked to all NULL libraries linked globally. This causes issue with StackCheckLib (though any NULL library being applied globally has the same issue) because BaseTools will attempt to link the library and add an extern to _ModuleEntryPoint, which does not exist for this module. Moving this module to USER_DEFINED instructs BaseTools to not link any NULL libraries to it, which is the desired behavior, and leads to a much cleaner global NULL library implementation, in this case for StackCheckLib. This change was tested on OVMF IA32/X64 and proved to work as before. Signed-off-by: Oliver Smith-Denny <osde@linux.microsoft.com>
Diffstat (limited to 'OvmfPkg')
0 files changed, 0 insertions, 0 deletions