All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anne Macedo <retpolanne@posteo.net>
To: qemu-devel@nongnu.org
Subject: Onboarding QEMU Firmware Configuration to other machines
Date: Sun, 24 Nov 2024 14:22:29 +0000	[thread overview]
Message-ID: <m2wmgsiudo.fsf@posteo.net> (raw)


Hello!

How should one port fw_cfg to other QEMU machines?

Context:

- I found a possible bug on the Debian builds for Raspberry Pi 4 that is
  only triggered when I try to launch it on QEMU;

- I wrote an issue on systemd (I thought it had something to do with
  logind) and they requested me to only fill bugs if they show up on the
  upstream.

- I tried baking systemd with mkosi – however, to test with mkosi and
  qemu, it uses fw_cfg [1] which seems specific to the virt machine on
  ARM.

- Opened an issue [2] and started working on that [3]

However, I still don't understand exactly how fw_cfg works. My current
understanding is that it is a device that, when connected some memory
mapping will happen on the guest so that it can access this memmap.

TL;DR which steps should I take to onboard fw_cfg to machines such as
raspi4b?

Thanks!
Anne


[1] https://github.com/systemd/mkosi/blob/6c33859a1b445e0bff19d9e7f28158140893a3e4/mkosi/config.py#L456

[2] https://gitlab.com/qemu-project/qemu/-/issues/2695

[3] https://gitlab.com/retpolanne/qemu/-/commit/86fca16555385c3685b7a1489a9cfaa255e148cf


             reply	other threads:[~2024-11-24 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24 14:22 Anne Macedo [this message]
2024-11-24 17:41 ` Onboarding QEMU Firmware Configuration to other machines Peter Maydell
2024-11-25  9:47   ` Daniel P. Berrangé

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=m2wmgsiudo.fsf@posteo.net \
    --to=retpolanne@posteo.net \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.