mirror of https://github.com/acidanthera/audk.git
437eb3f7a8
BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=2198 The flash detection routine will attempt to determine how the flash device behaves (e.g. ROM, RAM, Flash). But when SEV-ES is enabled and the flash device behaves as a ROM device (meaning it is marked read-only by the hypervisor), this check may result in an infinite nested page fault because of the attempted write. Since the instruction cannot be emulated when SEV-ES is enabled, the RIP is never advanced, resulting in repeated nested page faults. When SEV-ES is enabled, exit the flash detection early and assume that the FD behaves as Flash. This will result in QemuFlashWrite() being called to store EFI variables, which will also result in an infinite nested page fault when the write is performed. In this case, update QemuFlashWrite() to use the VMGEXIT MMIO write support to have the hypervisor perform the write without having to emulate the instruction. Cc: Jordan Justen <jordan.l.justen@intel.com> Cc: Laszlo Ersek <lersek@redhat.com> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com> Reviewed-by: Laszlo Ersek <lersek@redhat.com> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com> Regression-tested-by: Laszlo Ersek <lersek@redhat.com> |
||
|---|---|---|
| .. | ||
| FvbInfo.c | ||
| FvbServicesRuntimeDxe.inf | ||
| FvbServicesSmm.inf | ||
| FwBlockService.c | ||
| FwBlockService.h | ||
| FwBlockServiceDxe.c | ||
| FwBlockServiceSmm.c | ||
| QemuFlash.c | ||
| QemuFlash.h | ||
| QemuFlashDxe.c | ||
| QemuFlashSmm.c | ||