summaryrefslogtreecommitdiffstats
path: root/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.h
diff options
context:
space:
mode:
authorBrijesh Singh <brijesh.singh@amd.com>2018-07-06 10:00:41 -0500
committerLaszlo Ersek <lersek@redhat.com>2018-07-06 20:08:21 +0200
commit3b3d016b7b867d7e4782af9a6b54e110d155a1b3 (patch)
tree795bab01188cf8fa093ba11e006a26baff5ef9c3 /OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.h
parent966363d5a34839399e3d9f68d4f4efb4b1a9ec66 (diff)
downloadedk2-3b3d016b7b867d7e4782af9a6b54e110d155a1b3.tar.gz
edk2-3b3d016b7b867d7e4782af9a6b54e110d155a1b3.tar.bz2
edk2-3b3d016b7b867d7e4782af9a6b54e110d155a1b3.zip
OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Do not expose MMIO in SMM build
In the SMM build, only an SMM driver is using the address range hence we do not need to expose the flash MMIO range in EFI runtime mapping. Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Anthony Perard <anthony.perard@citrix.com> Cc: Julien Grall <julien.grall@linaro.org> Cc: Justen Jordan L <jordan.l.justen@intel.com> Cc: Laszlo Ersek <lersek@redhat.com> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> Reviewed-by: Laszlo Ersek <lersek@redhat.com> Regression-tested-by: Laszlo Ersek <lersek@redhat.com>
Diffstat (limited to 'OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.h')
-rw-r--r--OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.h7
1 files changed, 7 insertions, 0 deletions
diff --git a/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.h b/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.h
index 1f9287b087..178f578d49 100644
--- a/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.h
+++ b/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.h
@@ -189,4 +189,11 @@ VOID
InstallVirtualAddressChangeHandler (
VOID
);
+
+EFI_STATUS
+MarkIoMemoryRangeForRuntimeAccess (
+ IN EFI_PHYSICAL_ADDRESS BaseAddress,
+ IN UINTN Length
+ );
+
#endif