Branch: refs/heads/master
  Home:   https://github.com/tianocore/edk2
  Commit: 5c9f151e0c8c0a881bc374ec52fef07714735a82
      
https://github.com/tianocore/edk2/commit/5c9f151e0c8c0a881bc374ec52fef07714735a82
  Author: Sebastien Boeuf <sebastien.bo...@intel.com>
  Date:   2022-06-03 (Fri, 03 Jun 2022)

  Changed paths:
    A OvmfPkg/CloudHv/CloudHvDefines.fdf.inc
    M OvmfPkg/CloudHv/CloudHvX64.fdf

  Log Message:
  -----------
  OvmfPkg: CloudHv: Fix FW_BASE_ADDRESS

The FW_BASE_ADDRESS value provided by OvmfPkgDefines.fdf.inc is
incorrect for the CloudHv target. We know the generated firmware
contains a PVH ELF header, meaning it will be loaded according to the
address provided through this header. And since we know this address
isn't going to change as it's part of CloudHvElfHeader.fdf.inc, we can
hardcode it through a new include file CloudHvDefines.fdf.inc, which
replaces the generic one OvmfPkgDefines.fdf.inc.

With this change, we prevent the firmware from accessing MMIO addresses
from the address range 0xffc00000-0xffffffff since we know the firmware
hasn't been loaded on this address range.

Signed-off-by: Sebastien Boeuf <sebastien.bo...@intel.com>


  Commit: 43f3cfce19a713fd05cc5bc400b5bf6b79b19a9b
      
https://github.com/tianocore/edk2/commit/43f3cfce19a713fd05cc5bc400b5bf6b79b19a9b
  Author: Sebastien Boeuf <sebastien.bo...@intel.com>
  Date:   2022-06-03 (Fri, 03 Jun 2022)

  Changed paths:
    M OvmfPkg/Library/PlatformInitLib/Platform.c
    M OvmfPkg/Library/QemuBootOrderLib/QemuBootOrderLib.c

  Log Message:
  -----------
  OvmfPkg: Check for QemuFwCfg availability before accessing it

There are few places in the codebase assuming QemuFwCfg will be present
and supported, which can cause some issues when trying to rely on the
QemuFwCfgLibNull implementation of QemuFwCfgLib.

Signed-off-by: Sebastien Boeuf <sebastien.bo...@intel.com>
Acked-by: Jiewen Yao <jiewen....@intel.com>


  Commit: 3129ed374c72cb1dc84ab5467d03ab0180a4d108
      
https://github.com/tianocore/edk2/commit/3129ed374c72cb1dc84ab5467d03ab0180a4d108
  Author: Sebastien Boeuf <sebastien.bo...@intel.com>
  Date:   2022-06-03 (Fri, 03 Jun 2022)

  Changed paths:
    M OvmfPkg/CloudHv/CloudHvX64.dsc

  Log Message:
  -----------
  OvmfPkg: CloudHv: Rely on QemuFwCfgLibNull implementation

Since Cloud Hypervisor doesn't support the fw_cfg mechanism, it's more
appropriate to rely on QemuFwCfgLibNull implementation of QemuFwCfgLib
since it provides a null implementation that will not issue any PIO
accesses to ports 0x510 and 0x511.

Signed-off-by: Sebastien Boeuf <sebastien.bo...@intel.com>
Acked-by: Jiewen Yao <jiewen....@intel.com>


  Commit: bf25f27e0021ae1f37184fa8fc76382599e23012
      
https://github.com/tianocore/edk2/commit/bf25f27e0021ae1f37184fa8fc76382599e23012
  Author: Sebastien Boeuf <sebastien.bo...@intel.com>
  Date:   2022-06-03 (Fri, 03 Jun 2022)

  Changed paths:
    M OvmfPkg/Library/PlatformInitLib/Platform.c

  Log Message:
  -----------
  OvmfPkg: Don't access A20 gate register on Cloud Hypervisor

Since Cloud Hypervisor doesn't emulate an A20 gate register on I/O port
0x92, it's better to avoid accessing it when the platform is identified
as Cloud Hypervisor.

Signed-off-by: Sebastien Boeuf <sebastien.bo...@intel.com>
Acked-by: Jiewen Yao <jiewen....@intel.com>


Compare: https://github.com/tianocore/edk2/compare/632574ced10f...bf25f27e0021


_______________________________________________
edk2-commits mailing list
edk2-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-commits

Reply via email to