[Qemu-devel] expose QEMU's fw_cfg boot order to ARM guest firmware (Intel BDS)

[Laszlo Ersek <lersek@redhat.com>]

Hi,

this message is meant as a short, cross-posted thread starter, so that
both qemu- and edk2-side comments can be kept in one thread. I'll follow
up with two series:

- the first small series for qemu adds fw_cfg to the arm "virt" machine
  type in qemu, automatically exposing the "bootorder" fw_cfg file to
  the guest (when at least one bootindex=N device property is specified
  on the command line),

- the second, not so small, dependent series for edk2:
  - adds an MMIO-based fw_cfg client to the ARM guest firmware in edk2,
  - makes the OpenFirmware-to-UEFI devpath translation stuff in OvmfPkg
    reusable for the ArmVirtualizationQemu platform,
  - makes the virtio-pci specific bits in that logic conditional, and
    introduces (similarly conditional) coverage for virtio-mmio.

Thanks
Laszlo