OvmfPkg/QemuBootOrderLib: add ConnectDevicesFromQemu()

QemuBootOrderLib expects PlatformBootManagerLib to call the following
triplet:

(1) EfiBootManagerConnectAll(),
(2) EfiBootManagerRefreshAllBootOption(),
(3) SetBootOrderFromQemu().

This leads to bad performance, when many devices exist such that the
firmware can drive them, but they aren't marked for booting in the
"bootorder" fw_cfg file. Namely,

(1) EfiBootManagerConnectAll() talks to all hardware, which takes long.
    Plus some DriverBindingStart() functions write NV variables, which is
    also slow. (For example, the IP config policy for each NIC is stored
    in an NV var that is named after the MAC).

(2) EfiBootManagerRefreshAllBootOption() generates boot options from the
    protocol instances produced by (1). Writing boot options is slow.

(3) Under the above circumstances, SetBootOrderFromQemu() removes most of
    the boot options produced by (2). Erasing boot options is slow.

Introduce ConnectDevicesFromQemu() as a replacement for (1): only connect
devices that the QEMU user actually wants to boot off of.

(There's a slight loss of compatibility when a platform switches from
EfiBootManagerConnectAll() to ConnectDevicesFromQemu().
EfiBootManagerConnectAll() may produce UEFI device paths that are unknown
to QemuBootOrderLib (that is, for neither PCI- nor virtio-mmio-based
devices). The BootOrderComplete() function lets such unmatched boot
options survive at the end of the boot order. With
ConnectDevicesFromQemu(), these options will not be auto-generated in the
first place. They may still be produced by other means.

SetBootOrderFromQemu() is not modified in any way; reordering+filtering
boot options remains a separate task.)

Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Shannon Zhao <zhaoshenglong@huawei.com>
Cc: Xiang Zheng <xiang.zheng@linaro.org>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> # ArmVirtQemu
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Xiang Zheng <xiang.zheng@linaro.org>

1 files changed, 37 insertions, 2 deletions

diff --git a/OvmfPkg/Include/Library/QemuBootOrderLib.h b/OvmfPkg/Include/Library/QemuBootOrderLib.h
index 874344a95d..d17de3bb8f 100644
--- a/OvmfPkg/Include/Library/QemuBootOrderLib.h
+++ b/OvmfPkg/Include/Library/QemuBootOrderLib.h
@@ -21,6 +21,41 @@
 

 

 /**

+  Connect devices based on the boot order retrieved from QEMU.

+

+  Attempt to retrieve the "bootorder" fw_cfg file from QEMU. Translate the

+  OpenFirmware device paths therein to UEFI device path fragments. Connect the

+  devices identified by the UEFI devpath prefixes as narrowly as possible, then

+  connect all their child devices, recursively.

+

+  If this function fails, then platform BDS should fall back to

+  EfiBootManagerConnectAll(), or some other method for connecting any expected

+  boot devices.

+

+  @retval RETURN_SUCCESS            The "bootorder" fw_cfg file has been

+                                    parsed, and the referenced device-subtrees

+                                    have been connected.

+

+  @retval RETURN_UNSUPPORTED        QEMU's fw_cfg is not supported.

+

+  @retval RETURN_NOT_FOUND          Empty or nonexistent "bootorder" fw_cfg

+                                    file.

+

+  @retval RETURN_INVALID_PARAMETER  Parse error in the "bootorder" fw_cfg file.

+

+  @retval RETURN_OUT_OF_RESOURCES   Memory allocation failed.

+

+  @return                           Error statuses propagated from underlying

+                                    functions.

+**/

+RETURN_STATUS

+EFIAPI

+ConnectDevicesFromQemu (

+  VOID

+  );

+

+

+/**

 

   Set the boot order based on configuration retrieved from QEMU.

 

@@ -29,8 +64,8 @@
   translated fragments against the current list of boot options, and rewrite

   the BootOrder NvVar so that it corresponds to the order described in fw_cfg.

 

-  Platform BDS should call this function after EfiBootManagerConnectAll () and

-  EfiBootManagerRefreshAllBootOption () return.

+  Platform BDS should call this function after connecting any expected boot

+  devices and calling EfiBootManagerRefreshAllBootOption ().

 

   @retval RETURN_SUCCESS            BootOrder NvVar rewritten.