From: Markus Armbruster <armbru@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, "Eric Blake" <eblake@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Zhao Liu" <zhao1.liu@intel.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Dr. David Alan Gilbert" <dave@treblig.org>,
"Yanan Wang" <wangyanan55@huawei.com>
Subject: Re: [PATCH v6 1/3] hw/uefi: add query-firmware-log monitor command
Date: Wed, 22 Oct 2025 07:55:16 +0200 [thread overview]
Message-ID: <87plafiipn.fsf@pond.sub.org> (raw)
In-Reply-To: <20251017115006.2696991-2-kraxel@redhat.com> (Gerd Hoffmann's message of "Fri, 17 Oct 2025 13:50:03 +0200")
Gerd Hoffmann <kraxel@redhat.com> writes:
> 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 the query-firmware-log qmp monitor command to
> read the firmware log.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2025-10-22 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 11:50 [PATCH v6 0/3] hw/uefi: add support for receiving the firmware log via monitor Gerd Hoffmann
2025-10-17 11:50 ` [PATCH v6 1/3] hw/uefi: add query-firmware-log monitor command Gerd Hoffmann
2025-10-22 5:55 ` Markus Armbruster [this message]
2025-10-17 11:50 ` [PATCH v6 2/3] hw/uefi: add 'info firmware-log' hmp " Gerd Hoffmann
2025-10-17 11:50 ` [PATCH v6 3/3] hw/uefi/ovmf-log: add maxsize parameter Gerd Hoffmann
2025-10-22 5:57 ` Markus Armbruster
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=87plafiipn.fsf@pond.sub.org \
--to=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=philmd@linaro.org \
--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 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.