From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Yanan Wang <wangyanan55@huawei.com>,
Markus Armbruster <armbru@redhat.com>,
Fabiano Rosas <farosas@suse.de>, Eric Blake <eblake@redhat.com>,
"Dr. David Alan Gilbert" <dave@treblig.org>,
Laurent Vivier <lvivier@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Zhao Liu <zhao1.liu@intel.com>,
Eduardo Habkost <eduardo@habkost.net>
Subject: Re: [PATCH v3] hw/uefi: add "info firmware-log" + "query-firmware-log" monitor commands
Date: Mon, 13 Oct 2025 21:11:47 +0200 [thread overview]
Message-ID: <7300d719-e354-480f-9476-19e251a461b1@linaro.org> (raw)
In-Reply-To: <20251010071008.2555267-1-kraxel@redhat.com>
On 10/10/25 09:10, Gerd Hoffmann wrote:
> Starting with the edk2-stable202508 tag OVMF (and ArmVirt too) have
> optional support for logging to a memory buffer. There is guest side
> support -- for example in linux kernels v6.17+ -- to read that buffer.
> But that might not helpful if your guest stops booting early enough that
> guest tooling can not be used yet. So host side support to read that
> log buffer is a useful thing to have.
>
> This patch implements both qmp and hmp monitor commands to read the
> firmware log.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> include/monitor/hmp.h | 1 +
> hw/uefi/ovmf-log.c | 265 +++++++++++++++++++++++++++++++++++++
> tests/qtest/qmp-cmd-test.c | 2 +
> hmp-commands-info.hx | 14 ++
> hw/uefi/meson.build | 2 +-
> qapi/machine.json | 23 ++++
> 6 files changed, 306 insertions(+), 1 deletion(-)
> create mode 100644 hw/uefi/ovmf-log.c
At a glance, why not "info ovmf-log" and "query-ovmf-log"?
next prev parent reply other threads:[~2025-10-13 19:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 7:10 [PATCH v3] hw/uefi: add "info firmware-log" + "query-firmware-log" monitor commands Gerd Hoffmann
2025-10-10 9:12 ` Daniel P. Berrangé
2025-10-10 9:27 ` Gerd Hoffmann
2025-10-10 9:31 ` Daniel P. Berrangé
2025-10-13 8:42 ` Gerd Hoffmann
2025-10-10 11:41 ` Markus Armbruster
2025-10-10 17:36 ` Markus Armbruster
2025-10-10 20:23 ` Dr. David Alan Gilbert
2025-10-11 4:43 ` Markus Armbruster
2025-10-11 9:29 ` Markus Armbruster
2025-10-13 9:19 ` Gerd Hoffmann
2025-10-13 10:43 ` Markus Armbruster
2025-10-13 11:47 ` Gerd Hoffmann
2025-10-10 20:36 ` Dr. David Alan Gilbert
2025-10-13 11:55 ` Gerd Hoffmann
2025-10-13 13:12 ` Dr. David Alan Gilbert
2025-10-13 19:11 ` Philippe Mathieu-Daudé [this message]
2025-10-14 13:02 ` 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=7300d719-e354-480f-9476-19e251a461b1@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=dave@treblig.org \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--cc=kraxel@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.com \
--cc=zhao1.liu@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).