diff options
author | Lou, Yun <Yun.Lou@intel.com> | 2021-09-16 17:27:12 +0800 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2021-09-16 12:50:06 +0000 |
commit | 89f7ed8b29f6a88a8fb78d6fb2c92b4f7edf42d2 (patch) | |
tree | b682fe67e1e2f08f1ff8999e99c2693d2f7be456 /UefiCpuPkg/ResetVector/Vtf0/Vtf0.nasmb | |
parent | 010753b7e7cfb5ba2d1acd2200343cc4f55d7962 (diff) | |
download | edk2-89f7ed8b29f6a88a8fb78d6fb2c92b4f7edf42d2.tar.gz |
UefiCpuPkg: Prevent from re-initializing CPU features during S3 resume
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3621
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3631
Current CPU feature initialization design:
During normal boot, CpuFeaturesPei module (inside FSP) initializes the
CPU features. During S3 boot, CpuFeaturesPei module does nothing, and
CpuSmm driver (in SMRAM) initializes CPU features instead.
This code change prevents CpuSmm driver from re-initializing CPU
features during S3 resume if CpuFeaturesPei module has done the same
initialization.
In addition, EDK2 contains DxeIpl PEIM that calls S3RestoreConfig2 PPI
during S3 boot and this PPI eventually calls CpuSmm driver (in SMRAM) to
initialize the CPU features, so "EDK2 + FSP" does not have the CPU
feature initialization issue during S3 boot. But "coreboot" does not
contain DxeIpl PEIM and the issue appears, unless
"PcdCpuFeaturesInitOnS3Resume" is set to TRUE.
Signed-off-by: Jason Lou <yun.lou@intel.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Rahul Kumar <rahul1.kumar@intel.com>
Diffstat (limited to 'UefiCpuPkg/ResetVector/Vtf0/Vtf0.nasmb')
0 files changed, 0 insertions, 0 deletions