boot: Only do full driver initialization in VMs

Doing the reconnect dance on some real firmware creates huge delays on
boot. This should not be needed anymore as we now ask the firmware to
make console devices and xbootldr partitions available explicitly in a
more targeted fashion.

Fixes: #25510
This commit is contained in:
Jan Janssen
2022-11-29 15:05:56 +01:00
parent 7f19be808c
commit f6d59e2ebf
2 changed files with 4 additions and 6 deletions
-6
View File
@@ -2638,12 +2638,6 @@ EFI_STATUS efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *sys_table) {
/* Uncomment the next line if you need to wait for debugger. */
// debug_break();
/* The firmware may skip initializing some devices for the sake of a faster boot. This is especially
* true for fastboot enabled firmwares. But this means that things we use like input devices or the
* xbootldr partition may not be available yet. Reconnect all drivers should hopefully make the
* firmware initialize everything we need. */
(void) reconnect_all_drivers();
err = BS->OpenProtocol(image,
&LoadedImageProtocol,
(void **)&loaded_image,
+4
View File
@@ -83,6 +83,10 @@ EFI_STATUS vmm_open(EFI_HANDLE *ret_vmm_dev, EFI_FILE **ret_vmm_dir) {
assert(ret_vmm_dev);
assert(ret_vmm_dir);
/* Make sure all file systems have been initialized. Only do this in VMs as this is slow
* on some real firmwares. */
(void) reconnect_all_drivers();
/* find all file system handles */
err = BS->LocateHandleBuffer(ByProtocol, &FileSystemProtocol, NULL, &n_handles, &handles);
if (err != EFI_SUCCESS)