[svsm-devel] virtio-mmio base address: fw_cfg vs IGVM

Jörg Rödel joro at 8bytes.org
Wed Feb 19 17:24:53 CET 2025


Hi Oliver,

On Tue, Feb 18, 2025 at 08:04:49PM +0100, Oliver Steffen wrote:
> In last week's meeting we talked about communicating the mmio base address
> for the virtio driver to the SVSM via Qemu's fw_cfg interface.
> 
> This is easy to do, but now I am unsure how we want to
> handle hardware information in general.
> 
> Currently, the serial ports for logging, gdb, etc. are configured via
> the IGVM file.

That is right, but I consider IGVM parameters more of a workaround than a real
interface for communicating hardware specifics from the hypervisor to
the SVSM.

For the console it is not really important because a) A serial port can
easily be shared between SVSM and guest OS, and b) Mid-term the SVSM
will not use the serial port in release builds anyway.

So, in addition to what Jon wrote, I don't want to extend the IGVM
parameters for this matter. A "cleanly layered" solution would be much more
complicated (I think we discussed that in the meeting as well):

	1. Let SVSM consume ACPI tables from Hypervisor (e.g. via FWCFG)
	2. SVSM takes the devices it wants
	3. SVSM removes these devices from ACPI tables and forwards the
	   resulting tables to OVMF.

That is much more effort so I think for now all is well and we are okay
with QEMU communicating SVSM specific devices via FWCFG, so that the OS
will not see them.

Regards,

	Joerg


More information about the Svsm-devel mailing list