From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "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>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Dr. David Alan Gilbert" <dave@treblig.org>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: [PATCH v6 3/3] hw/uefi/ovmf-log: add maxsize parameter
Date: Fri, 17 Oct 2025 13:50:05 +0200 [thread overview]
Message-ID: <20251017115006.2696991-4-kraxel@redhat.com> (raw)
In-Reply-To: <20251017115006.2696991-1-kraxel@redhat.com>
Allow limiting the amount of log output sent. Allow up to 1 MiB.
In case the guest log buffer is larger than 1 MiB limit the output
instead of throwing an error.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/uefi/ovmf-log.c | 42 ++++++++++++++++++++++++++++++++++--------
hmp-commands-info.hx | 4 ++--
qapi/machine.json | 5 +++++
3 files changed, 41 insertions(+), 10 deletions(-)
diff --git a/hw/uefi/ovmf-log.c b/hw/uefi/ovmf-log.c
index fe8acbd19236..98ebb0209491 100644
--- a/hw/uefi/ovmf-log.c
+++ b/hw/uefi/ovmf-log.c
@@ -18,6 +18,7 @@
#include "qapi/error.h"
#include "qapi/type-helpers.h"
#include "qapi/qapi-commands-machine.h"
+#include "qobject/qdict.h"
/* ----------------------------------------------------------------------- */
@@ -164,7 +165,8 @@ static void handle_ovmf_log_range(GString *out,
}
}
-FirmwareLog *qmp_query_firmware_log(Error **errp)
+FirmwareLog *qmp_query_firmware_log(bool have_max_size, uint64_t max_size,
+ Error **errp)
{
MEM_DEBUG_LOG_HDR header;
dma_addr_t offset, base;
@@ -184,18 +186,40 @@ FirmwareLog *qmp_query_firmware_log(Error **errp)
return NULL;
}
- if (header.DebugLogSize > MiB) {
- /* default size is 128k (32 pages), allow up to 1M */
- error_setg(errp, "firmware log: log buffer is too big");
- return NULL;
- }
-
if (header.DebugLogHeadOffset > header.DebugLogSize ||
header.DebugLogTailOffset > header.DebugLogSize) {
error_setg(errp, "firmware log buffer header is invalid");
return NULL;
}
+ if (have_max_size) {
+ if (max_size > MiB) {
+ error_setg(errp, "parameter 'max-size' exceeds 1MiB");
+ return NULL;
+ }
+ } else {
+ max_size = MiB;
+ }
+
+ /* adjust header.DebugLogHeadOffset so we return at most maxsize bytes */
+ if (header.DebugLogHeadOffset > header.DebugLogTailOffset) {
+ /* wrap around */
+ if (header.DebugLogTailOffset > max_size) {
+ header.DebugLogHeadOffset = header.DebugLogTailOffset - max_size;
+ } else {
+ uint64_t max_chunk = max_size - header.DebugLogTailOffset;
+ if (header.DebugLogSize > max_chunk &&
+ header.DebugLogHeadOffset < header.DebugLogSize - max_chunk) {
+ header.DebugLogHeadOffset = header.DebugLogSize - max_chunk;
+ }
+ }
+ } else {
+ if (header.DebugLogTailOffset > max_size &&
+ header.DebugLogHeadOffset < header.DebugLogTailOffset - max_size) {
+ header.DebugLogHeadOffset = header.DebugLogTailOffset - max_size;
+ }
+ }
+
base = offset + header.HeaderSize;
if (header.DebugLogHeadOffset > header.DebugLogTailOffset) {
/* wrap around */
@@ -239,8 +263,10 @@ void hmp_info_firmware_log(Monitor *mon, const QDict *qdict)
Error *err = NULL;
FirmwareLog *log;
gsize log_len;
+ int64_t maxsize;
- log = qmp_query_firmware_log(&err);
+ maxsize = qdict_get_try_int(qdict, "max-size", -1);
+ log = qmp_query_firmware_log(maxsize != -1, (uint64_t)maxsize, &err);
if (err) {
hmp_handle_error(mon, err);
return;
diff --git a/hmp-commands-info.hx b/hmp-commands-info.hx
index 33cf740bbc1b..2a7f5810d706 100644
--- a/hmp-commands-info.hx
+++ b/hmp-commands-info.hx
@@ -998,8 +998,8 @@ ERST
{
.name = "firmware-log",
- .args_type = "",
- .params = "",
+ .args_type = "max-size:o?",
+ .params = "[max-size]",
.help = "show the firmware (ovmf) debug log",
.cmd = hmp_info_firmware_log,
},
diff --git a/qapi/machine.json b/qapi/machine.json
index 96133e5c71cf..c6dc6fe69b5c 100644
--- a/qapi/machine.json
+++ b/qapi/machine.json
@@ -1858,9 +1858,14 @@
#
# Find firmware memory log buffer in guest memory, return content.
#
+# @max-size: limit the amount of log data returned. Up to 1 MiB of
+# log data is allowed. In case the amount of log data is
+# larger than @max-size the tail of the log is returned.
+#
# Since: 10.2
##
{ 'command': 'query-firmware-log',
+ 'data': { '*max-size': 'size' },
'returns': 'FirmwareLog' }
##
--
2.51.0
next prev parent reply other threads:[~2025-10-17 11:51 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
2025-10-17 11:50 ` [PATCH v6 2/3] hw/uefi: add 'info firmware-log' hmp " Gerd Hoffmann
2025-10-17 11:50 ` Gerd Hoffmann [this message]
2025-10-22 5:57 ` [PATCH v6 3/3] hw/uefi/ovmf-log: add maxsize parameter 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=20251017115006.2696991-4-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=dave@treblig.org \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--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 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).