diff options
author | Zhiguang Liu <zhiguang.liu@intel.com> | 2023-07-10 09:47:50 +0800 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2023-09-18 02:39:25 +0000 |
commit | db38c7de64d4dda2bf3cc6e5d764b027b00afa59 (patch) | |
tree | afa9b7311873e8002e880861192621da84fb0757 /MdeModulePkg | |
parent | dea6002d6e612ee3066fc755b5ad47558d84d645 (diff) | |
download | edk2-db38c7de64d4dda2bf3cc6e5d764b027b00afa59.tar.gz edk2-db38c7de64d4dda2bf3cc6e5d764b027b00afa59.tar.bz2 edk2-db38c7de64d4dda2bf3cc6e5d764b027b00afa59.zip |
UefiCpuPkg/ResetVector: Remove AP waking vector from ResetVector
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4494
Current reset vector uses 0xffffffe0 as AP waking vector, and expects
GenFv generates code aligned on a 4k boundary which will jump to this
location. However, some issues are listed below
1. GenFV doesn't generate code as the comment expects, because GenFv
assumes no modifications are required to the VTF-0 'Volume Top File'.
2. Even if removing VFT0 signature and let GenFv to modify, Genfv is
hard-code using another flash address 0xffffffd0.
3. In the same patch series, AP waking vector code is removed from
GenFv, because no such usage anymore. The existing of first two issues
also approve the usage is not available for a long time.
Therefore, remove AP waking vector related code.
Cc: Eric Dong <eric.dong@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: Rahul Kumar <rahul1.kumar@intel.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
Signed-off-by: Zhiguang Liu <zhiguang.liu@intel.com>
Diffstat (limited to 'MdeModulePkg')
0 files changed, 0 insertions, 0 deletions