Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 Apr 2023 07:54:21 +1000
From:      Peter Grehan <grehan@freebsd.org>
To:        =?UTF-8?Q?Corvin_K=c3=b6hne?= <corvink@FreeBSD.org>
Cc:        virtualization@FreeBSD.org
Subject:   Re: [PATCH] OvmfPkg/BhyveBhf: install bhyve's ACPI tables
Message-ID:  <365212d5-75e4-1717-b69a-5e1ddf6e40ab@freebsd.org>
In-Reply-To: <e539403193518c7dd744741410be632947414213.camel@FreeBSD.org>
References:  <20230331123936.540020-1-corvink@FreeBSD.org> <a2e19eb1-bb85-84f6-f805-c8065076bbf0@freebsd.org> <e539403193518c7dd744741410be632947414213.camel@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> Using the qemu fwcfg has one big disadvantage:
> Bhyve's fwctl and qemu's fwcfg can't be used at the same time. Due to
> backward compatibility reasons, bhyve uses fwctl as default. So, using
> qemu's fwcfg to locate the rsdp only works, if the user changes his
> bhyve call.
> I don't want to use fwctl to locate the rsdp because IMHO we should
> migrate to fwcfg. So, we shouldn't add new features to fwctl.

  Ah ok.

> Btw: I'm also preparing some patches to support qemu's acpi table
> loader. So, if we like to use qemu's fwcfg, we should use the loader
> instead of an own baked solution.

  Yes: that's a much better solution. The bhyve-generated ones are very 
size-limited.

later,

Peter.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?365212d5-75e4-1717-b69a-5e1ddf6e40ab>