diff options
author | Corvin Köhne <corvink@freebsd.org> | 2023-06-06 11:21:39 +0200 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2023-06-06 10:55:41 +0000 |
commit | 4bd0849d81b48233196092868081315ec4d9233d (patch) | |
tree | 0d49d309cfe738d788c9c57027a880ec90360a44 /.pytool | |
parent | 1288c5415c81af7b184567c7cb02b59aeb662be9 (diff) | |
download | edk2-4bd0849d81b48233196092868081315ec4d9233d.zip edk2-4bd0849d81b48233196092868081315ec4d9233d.tar.gz edk2-4bd0849d81b48233196092868081315ec4d9233d.tar.bz2 |
OvmfPkg/Bhyve: install ACPI tables from memory
It's much easier to create configuration dependent ACPI tables for bhyve
than for OVMF. For this reason, don't use the statically created ACPI
tables provided by OVMF. Instead, prefer the dynamically created ACPI
tables of bhyve. If bhyve provides no ACPI tables or we are unable to
detect those, fall back to OVMF tables.
Ideally, we use the qemu fwcfg interface to pass the ACPI tables from
bhyve to OVMF. bhyve will support this in the future. However, current
bhyve executables don't support passing ACPI tables by the qemu fwcfg
interface. They just copy the ACPI into main memory. For that reason,
pick up the ACPI tables from main memory.
Signed-off-by: Corvin Köhne <corvink@FreeBSD.org>
Reviewed-by: Rebecca Cran <rebecca@bsdio.com>
Acked-by: Peter Grehan <grehan@freebsd.org>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to '.pytool')
0 files changed, 0 insertions, 0 deletions