mirror of https://github.com/acidanthera/audk.git
da58d987cc
In the PEI fw_cfg instance: - QemuFwCfgS3Enabled() queries S3 enablement via fw_cfg. This behavior is shared with the DXE fw_cfg instance, and the PEI fw_cfg instance already pulls in the function from "QemuFwCfgS3PeiDxe.c". - If QemuFwCfgS3Enabled() returns TRUE, the client module is permitted to call QemuFwCfgS3CallWhenBootScriptReady(). However, in the PEI phase we have no support for capturing ACPI S3 Boot Script opcodes, hence we return RETURN_UNSUPPORTED unconditionally. This behavior is unique to the PEI fw_cfg instance, so add the function to "QemuFwCfgS3Pei.c". - Consequently, the QemuFwCfgS3ScriptWriteBytes(), QemuFwCfgS3ScriptReadBytes(), QemuFwCfgS3ScriptSkipBytes(), and QemuFwCfgS3ScriptCheckValue() functions must never be called. (They could only be called from the client module's callback, but QemuFwCfgS3CallWhenBootScriptReady() will never install such callback in the PEI fw_cfg instance -- see above.) This behavior is not unique to the PEI fw_cfg instance (it is shared with the Base Null instance), so pull in these functions from "QemuFwCfgS3BasePei.c". Cc: Jordan Justen <jordan.l.justen@intel.com> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=394 Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> |
||
|---|---|---|
| .. | ||
| AcpiTimerLib | ||
| DxePciLibI440FxQ35 | ||
| EmuVariableFvbLib | ||
| LoadLinuxLib | ||
| LockBoxLib | ||
| NvVarsFileLib | ||
| PciHostBridgeLib | ||
| PlatformBootManagerLib | ||
| PlatformDebugLibIoPort | ||
| PlatformFvbLibNull | ||
| PlatformSecureLib | ||
| QemuBootOrderLib | ||
| QemuFwCfgLib | ||
| QemuFwCfgS3Lib | ||
| ResetSystemLib | ||
| SerializeVariablesLib | ||
| SmbiosVersionLib | ||
| SmmCpuFeaturesLib | ||
| VirtioLib | ||
| VirtioMmioDeviceLib | ||
| XenConsoleSerialPortLib | ||
| XenHypercallLib | ||
| XenIoMmioLib | ||