From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Jason Wang <jasowang@redhat.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Andrew Melnychenko <andrew@daynix.com>
Subject: Re: [PATCH 3/5] ebpf: add formal error reporting to all APIs
Date: Tue, 6 Aug 2024 17:11:55 +0200 [thread overview]
Message-ID: <208ede45-0866-4dce-b6ef-e8390c1c56c1@linaro.org> (raw)
In-Reply-To: <20240806145653.1632478-4-berrange@redhat.com>
On 6/8/24 16:56, Daniel P. Berrangé wrote:
> The eBPF code is currently reporting error messages through trace
> events. Trace events are fine for debugging, but they are not to be
> considered the primary error reporting mechanism, as their output
> is inaccessible to callers.
>
> This adds an "Error **errp" parameter to all methods which have
> important error scenarios to report to the caller.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> ebpf/ebpf_rss.c | 59 ++++++++++++++++++++++++++++++++++++---------
> ebpf/ebpf_rss.h | 10 +++++---
> hw/net/virtio-net.c | 7 +++---
> 3 files changed, 59 insertions(+), 17 deletions(-)
>
> diff --git a/ebpf/ebpf_rss.c b/ebpf/ebpf_rss.c
> index aa7170d997..59854c8b51 100644
> --- a/ebpf/ebpf_rss.c
> +++ b/ebpf/ebpf_rss.c
> @@ -47,13 +47,14 @@ bool ebpf_rss_is_loaded(struct EBPFRSSContext *ctx)
> return ctx != NULL && (ctx->obj != NULL || ctx->program_fd != -1);
> }
>
> -static bool ebpf_rss_mmap(struct EBPFRSSContext *ctx)
> +static bool ebpf_rss_mmap(struct EBPFRSSContext *ctx, Error **errp)
> {
> ctx->mmap_configuration = mmap(NULL, qemu_real_host_page_size(),
> PROT_READ | PROT_WRITE, MAP_SHARED,
> ctx->map_configuration, 0);
> if (ctx->mmap_configuration == MAP_FAILED) {
> trace_ebpf_error("eBPF RSS", "can not mmap eBPF configuration array");
> + error_setg(errp, "Unable to map eBPF configuration array");
> return false;
> }
> ctx->mmap_toeplitz_key = mmap(NULL, qemu_real_host_page_size(),
> @@ -61,6 +62,7 @@ static bool ebpf_rss_mmap(struct EBPFRSSContext *ctx)
> ctx->map_toeplitz_key, 0);
> if (ctx->mmap_toeplitz_key == MAP_FAILED) {
> trace_ebpf_error("eBPF RSS", "can not mmap eBPF toeplitz key");
> + error_setg(errp, "Unable to map eBPF toeplitz array");
> goto toeplitz_fail;
> }
> ctx->mmap_indirections_table = mmap(NULL, qemu_real_host_page_size(),
> @@ -68,6 +70,7 @@ static bool ebpf_rss_mmap(struct EBPFRSSContext *ctx)
> ctx->map_indirections_table, 0);
> if (ctx->mmap_indirections_table == MAP_FAILED) {
> trace_ebpf_error("eBPF RSS", "can not mmap eBPF indirection table");
> + error_setg(errp, "Unable to map eBPF indirection array");
Aren't these trace_ebpf_error() calls redundant now?
> goto indirection_fail;
> }
next prev parent reply other threads:[~2024-08-06 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 14:56 [PATCH 0/5] Report fatal errors from failure with pre-opened eBPF RSS FDs Daniel P. Berrangé
2024-08-06 14:56 ` [PATCH 1/5] hw/net: fix typo s/epbf/ebpf/ in virtio-net Daniel P. Berrangé
2024-08-06 15:10 ` Philippe Mathieu-Daudé
2024-08-06 14:56 ` [PATCH 2/5] ebpf: drop redundant parameter checks in static methods Daniel P. Berrangé
2024-08-06 14:56 ` [PATCH 3/5] ebpf: add formal error reporting to all APIs Daniel P. Berrangé
2024-08-06 15:11 ` Philippe Mathieu-Daudé [this message]
2024-08-06 15:20 ` Daniel P. Berrangé
2024-08-07 7:37 ` Philippe Mathieu-Daudé
2024-08-07 7:39 ` Philippe Mathieu-Daudé
2024-08-07 9:13 ` Daniel P. Berrangé
2024-08-06 14:56 ` [PATCH 4/5] hw/net: report errors from failing to use eBPF RSS FDs Daniel P. Berrangé
2024-08-06 14:56 ` [PATCH 5/5] ebpf: improve trace event coverage to all key operations 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=208ede45-0866-4dce-b6ef-e8390c1c56c1@linaro.org \
--to=philmd@linaro.org \
--cc=andrew@daynix.com \
--cc=berrange@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yuri.benditovich@daynix.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).