From: "Cédric Le Goater" <clg@redhat.com>
To: qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v3 1/7] util/error: Introduce warn_report_err_once()
Date: Mon, 10 Feb 2025 17:26:48 +0100 [thread overview]
Message-ID: <c7ce5f30-ee52-46c8-b968-08ba01214a3e@redhat.com> (raw)
In-Reply-To: <20250206131438.1505542-2-clg@redhat.com>
On 2/6/25 14:14, Cédric Le Goater wrote:
> Depending on the configuration of the host and VM, a passthrough
> device may generate recurring DMA mapping errors at runtime. In such
> cases, reporting the issue once is sufficient.
>
> We have already the warn/error_report_once() routines taking a format
> and arguments. Using the same design pattern, add a new warning
> variant taking an 'Error *' parameter.
>
> Cc: Markus Armbruster <armbru@redhat.com>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
> ---
> include/qapi/error.h | 12 ++++++++++++
> util/error.c | 11 +++++++++++
> 2 files changed, 23 insertions(+)
Hello Markus,
Are you ok with this change ? Should we take it through the vfio queue ?
Thanks,
C.
> diff --git a/include/qapi/error.h b/include/qapi/error.h
> index 71f8fb2c50eee9a544992d0c05263c9793956fe1..f5fe2162623e5770d652f7415ebc25172d97616e 100644
> --- a/include/qapi/error.h
> +++ b/include/qapi/error.h
> @@ -466,6 +466,18 @@ void warn_reportf_err(Error *err, const char *fmt, ...)
> void error_reportf_err(Error *err, const char *fmt, ...)
> G_GNUC_PRINTF(2, 3);
>
> +/*
> + * Similar to warn_report_err(), except it prints the message just once.
> + * Return true when it prints, false otherwise.
> + */
> +bool warn_report_err_once_cond(bool *printed, Error *err);
> +
> +#define warn_report_err_once(err) \
> + ({ \
> + static bool print_once_; \
> + warn_report_err_once_cond(&print_once_, err); \
> + })
> +
> /*
> * Just like error_setg(), except you get to specify the error class.
> * Note: use of error classes other than ERROR_CLASS_GENERIC_ERROR is
> diff --git a/util/error.c b/util/error.c
> index e5e247209a9e0796074a9794f5598325f22f8d35..673011b89e95f488817b86c31cd389386b2558bb 100644
> --- a/util/error.c
> +++ b/util/error.c
> @@ -247,6 +247,17 @@ void warn_report_err(Error *err)
> error_free(err);
> }
>
> +bool warn_report_err_once_cond(bool *printed, Error *err)
> +{
> + if (*printed) {
> + error_free(err);
> + return false;
> + }
> + *printed = true;
> + warn_report_err(err);
> + return true;
> +}
> +
> void error_reportf_err(Error *err, const char *fmt, ...)
> {
> va_list ap;
next prev parent reply other threads:[~2025-02-10 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 13:14 [PATCH v3 0/7] vfio: Improve error reporting when MMIO region mapping fails Cédric Le Goater
2025-02-06 13:14 ` [PATCH v3 1/7] util/error: Introduce warn_report_err_once() Cédric Le Goater
2025-02-10 16:26 ` Cédric Le Goater [this message]
2025-02-11 6:53 ` Markus Armbruster
2025-02-06 13:14 ` [PATCH v3 2/7] vfio/pci: Replace "iommu_device" by "vIOMMU" Cédric Le Goater
2025-02-06 13:14 ` [PATCH v3 3/7] vfio: Rephrase comment in vfio_listener_region_add() error path Cédric Le Goater
2025-02-06 13:14 ` [PATCH v3 4/7] vfio: Introduce vfio_get_vfio_device() Cédric Le Goater
2025-02-06 13:14 ` [PATCH v3 5/7] vfio: Improve error reporting when MMIO region mapping fails Cédric Le Goater
2025-02-06 13:14 ` [PATCH v3 6/7] vfio: Remove reports of DMA mapping errors in backends Cédric Le Goater
2025-02-06 13:14 ` [PATCH v3 7/7] vfio: Remove superfluous error report in vfio_listener_region_add() Cédric Le Goater
2025-02-06 15:07 ` Harsh Prateek Bora
2025-02-10 16:01 ` [PATCH v3 0/7] vfio: Improve error reporting when MMIO region mapping fails Alex Williamson
2025-02-11 13:32 ` Cédric Le Goater
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=c7ce5f30-ee52-46c8-b968-08ba01214a3e@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--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 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).