On 13 March 2018 at 21:22, Laszlo Ersek <ler...@redhat.com> wrote: > Repo: https://github.com/lersek/edk2.git > Branch: qemu_bootorder_connect > > Adding tens or hundreds of bootable devices to a QEMU VM config slows > the OVMF and ArmVirtQemu boots to a crawl, several people have reported > in the past. > > There are at least two reasons for this (high pflash traffic due to > heavy nvvar massaging per device, and PCI config space access slowing > down on QEMU as the number of regions increases). However, part of the > pain is self-inflicted in our PlatformBootManagerLib instances: we > connect all bootable devices (for maximum compatibility with the user's > VM config) even if the user doesn't intend to boot off most of them. > > It's oft repeated that the set of devices connected during boot is > platform policy, so this series replaces the culprit > EfiBootManagerConnectAll() calls with a bit smarter algorithm. > > I sought to keep the commit messages under control. >
This is really nice. Most platforms I've worked with just connect everything all the time, which is sloppy. I'm glad you fixed this for *VMF Tested-by: Ard Biesheuvel <ard.biesheu...@linaro.org> # ArmVirtQemu Reviewed-by: Ard Biesheuvel <ard.biesheu...@linaro.org> _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
