summaryrefslogtreecommitdiff
path: root/IntelFsp2Pkg
diff options
context:
space:
mode:
authorPhil Noh <Phil.Noh@amd.com>2025-09-02 12:25:13 -0500
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2025-09-04 14:31:57 +0000
commit65485e195f37653bbbc06db2001c3a189d468666 (patch)
tree100e11cf9c692501ec34290693aa4f52d113c88c /IntelFsp2Pkg
parent1dacf4c40825e184f08be4d3041dc9e2be4d3c5c (diff)
downloadedk2-master.zip
edk2-master.tar.gz
edk2-master.tar.bz2
UefiCpuPkg/MpInitLib: Ensure AP wake up on WakeUpByInitSipiSipi modeHEADmaster
If AP loop mode is not Halt loop, it is found that the AP in ApInitDone state exits the loop mode immediately when WAKEUP_AP_SIGNAL is signaled at the first step of AP wake up. When WakeUpByInitSipiSipi is enabled, it is possible that the AP could clear StartupApSignal buffer before the BSP sends Init-Startup IPI to the AP. In the case, it causes that the BSP frees AP reset vector buffer even though AP wake up is in process. This results in an exception error. To ensure AP wake up, it is expected that the AP is in the known non-executable state before the AP wakeup signal. The issue happens when the AP is disabled through the MP service of gEfiMpServiceProtocolGuid->EnableDisableAP(FALSE) and enabled later through gEfiMpServiceProtocolGuid->EnableDisableAP(TRUE). In the flow, the AP that in MINOTOR-MWAIT-Loop or Run-Loop can respond to the WAKEUP_AP_SIGNAL before the BSP sends the INIT-SIPI-SIPI. Signed-off-by: Phil Noh <Phil.Noh@amd.com>
Diffstat (limited to 'IntelFsp2Pkg')
0 files changed, 0 insertions, 0 deletions