The ACPI_CPU_DATA structure is populated by Quark_EDKII_v1.1.0/IA32FamilyCpuBasePkg/CpuMpDxe, which we do not plan to import as a whole.
CpuMpDxe allocates ACPI_CPU_DATA in AcpiNVS memory (below 4GB), populates it carefully, and passes its address to PiSmmCpuDxeSmm via a dynamic PCD, PcdCpuS3DataAddress. This all happens when CpuMpDxe sees EFI_SMM_CONFIGURATION_PROTOCOL being installed. PiSmmCpuDxeSmm then copies this data into SMRAM (from AcpiNVS) when it receives the SMM-ready-to-lock notification. Finally, on S3 resume, the data is reused from SMRAM (when the S3 Resume PEIM transfers control to the SMRAM-hosted PiSmmCpuDxeSmm driver), in order to reinitialize CPU states. The ACPI_CPU_DATA.APState is never used by PiSmmCpuDxeSmm, so drop it. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <[email protected]> --- OvmfPkg/QuarkPort/Include/AcpiCpuData.h | 1 - 1 file changed, 1 deletion(-) diff --git a/OvmfPkg/QuarkPort/Include/AcpiCpuData.h b/OvmfPkg/QuarkPort/Include/AcpiCpuData.h index 5818743..dbecc1a 100644 --- a/OvmfPkg/QuarkPort/Include/AcpiCpuData.h +++ b/OvmfPkg/QuarkPort/Include/AcpiCpuData.h @@ -35,7 +35,6 @@ #define _ACPI_CPU_DATA_H_ typedef struct { - BOOLEAN APState; EFI_PHYSICAL_ADDRESS StartupVector; EFI_PHYSICAL_ADDRESS GdtrProfile; EFI_PHYSICAL_ADDRESS IdtrProfile; -- 1.8.3.1 _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
