diff options
author | Eric Dong <eric.dong@intel.com> | 2018-08-10 10:28:50 +0800 |
---|---|---|
committer | Eric Dong <eric.dong@intel.com> | 2018-08-16 08:42:00 +0800 |
commit | fcd92f16af8fd61d220fbd58af3198083180ae6e (patch) | |
tree | a432fcb5c631158999583f74f35a88f3b75ac749 /BaseTools/Source/Python/Ecc | |
parent | 293f876618c319ca08687e55e126332216185ad6 (diff) | |
download | edk2-fcd92f16af8fd61d220fbd58af3198083180ae6e.tar.gz edk2-fcd92f16af8fd61d220fbd58af3198083180ae6e.tar.bz2 edk2-fcd92f16af8fd61d220fbd58af3198083180ae6e.zip |
UefiCpuPkg/AcpiCpuData.h: Remove AcpiNVS and Below 4G limitation.
ACPI_CPU_DATA structure first introduced to save data in
normal boot phase. Also this data will be used in S3 phase
by one PEI driver. So in first phase, this data is been
defined to use ACPI NVS memory type and must below 4G.
Later in order to fix potential security issue,
PiSmmCpuDxeSmm driver added logic to copy ACPI_CPU_DATA
(except ResetVector and Stack buffer) to smram at smm
ready to lock point. ResetVector must below 1M and Stack
buffer is write only in S3 phase, so these two fields not
copy to smram. Also PiSmmCpuDxeSmm driver owned the task
to restore the CPU setting and it's a SMM driver.
After above change, the acpi nvs memory type and below 4G
limitation is no longer needed.
This change remove the limitation in the comments for
ACPI_CPU_DATA definition.
Cc: Marvin Häuser <Marvin.Haeuser@outlook.com>
Cc: Fan Jeff <vanjeff_919@hotmail.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ruiyu Ni <ruiyu.ni@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Eric Dong <eric.dong@intel.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
Tested-by: Laszlo Ersek <lersek@redhat.com>
Diffstat (limited to 'BaseTools/Source/Python/Ecc')
0 files changed, 0 insertions, 0 deletions