Coconut-SVSM development mailing list
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: Oliver Steffen <osteffen@redhat.com>
Cc: svsm-devel@coconut-svsm.dev,
	Stefano Garzarella <sgarzare@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [svsm-devel] virtio-mmio base address: fw_cfg vs IGVM
Date: Wed, 19 Feb 2025 17:24:53 +0100	[thread overview]
Message-ID: <Z7YF1fSQSp9BrJrx@8bytes.org> (raw)
In-Reply-To: <CA+bRGFprMx2s6scqXgjdrDUG2JOz0ybp6Srx0g1kp2ahSCoJuA@mail.gmail.com>

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

      parent reply	other threads:[~2025-02-19 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 19:04 [svsm-devel] virtio-mmio base address: fw_cfg vs IGVM Oliver Steffen
2025-02-18 21:01 ` [svsm-devel] [EXTERNAL] " Jon Lange
2025-02-19 16:24 ` Jörg Rödel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z7YF1fSQSp9BrJrx@8bytes.org \
    --to=joro@8bytes.org \
    --cc=kraxel@redhat.com \
    --cc=osteffen@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=svsm-devel@coconut-svsm.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox