Consistently use CONFIG_COREBOOT, CONFIG_QEMU, and runningOnXen().

CONFIG_QEMU means compile to start from QEMU (and possibly
Xen/KVM/Bochs) and definitely running under QEMU (or Xen/KVM/Bochs).

CONFIG_COREBOOT means compile for coreboot and definitely running
under coreboot.  Places that used CONFIG_COREBOOT to mean "running on
real hardware" have been changed to use !CONFIG_QEMU.

CONFIG_QEMU_HARDWARE enables support for some virtual hardware devices
even if QEMU didn't start SeaBIOS.

usingXen() is replaced by runningOnXen().

runningOnQEMU() is added to hardware devices that are only safe to
access when we are sure we are running under QEMU (or Xen/KVM/Bochs).
Neither the coreboot nor the csm code currently enable runningOnQEMU,
but future patches may.

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/post.c b/src/post.c
index 6c4ff70e..2c5e34e6 100644
--- a/src/post.c
+++ b/src/post.c
@@ -179,7 +179,7 @@ platform_hardware_setup(void)
     // Setup external BIOS interface tables
     if (CONFIG_COREBOOT)
         coreboot_biostable_setup();
-    else if (usingXen())
+    else if (runningOnXen())
         xen_biostable_setup();
     else
         qemu_biostable_setup();
@@ -319,7 +319,7 @@ dopost(void)
     qemu_cfg_preinit();
     if (CONFIG_COREBOOT)
         coreboot_preinit();
-    else if (usingXen())
+    else if (runningOnXen())
         xen_ramsize_preinit();
     else
         qemu_ramsize_preinit();