diff options
author | Tom Lendacky <thomas.lendacky@amd.com> | 2023-11-07 06:45:31 +0800 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2023-11-28 11:07:59 +0000 |
commit | 3c5f9ac5c3b92bf63b3c0a39658f0ae991e8436d (patch) | |
tree | eb24a793b70d398e5224818b7b5e221f54dc806d /OvmfPkg/AmdSev | |
parent | 447798cd3a78c8bfc5adb90254d50d22a838b301 (diff) | |
download | edk2-3c5f9ac5c3b92bf63b3c0a39658f0ae991e8436d.tar.gz edk2-3c5f9ac5c3b92bf63b3c0a39658f0ae991e8436d.tar.bz2 edk2-3c5f9ac5c3b92bf63b3c0a39658f0ae991e8436d.zip |
UefiCpuPkg/MpInitLib: Copy SEV-ES save area pointer during APIC ID sorting
With SEV-SNP, the SEV-ES save area for a vCPU should be unique to that
vCPU. After commit 3323359a811a, the VMSA allocation was re-used, but when
sorting the CPUs by APIC ID, the save area was not updated to follow the
original CPU. Similar to the StartupApSignal address, the SevEsSaveArea
address should be updated when sorting the CPUs.
This does not cause an issue at this time because all APs are in HLT state
and then are (re)started at the same time, with the same VMSA contents.
However, this should be fixed to account for any change in future
behavior.
Fixes: 3323359a811a ("UefiCpuPkg/MpInitLib: Reuse VMSA allocation to ...")
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
Diffstat (limited to 'OvmfPkg/AmdSev')
0 files changed, 0 insertions, 0 deletions