Browse Source
A design pattern of
trace_foo_error("descriptive string")
is undesirable because it does not allow for filtering trace events
based on the error scenario. Split eBPF error trace event into three
separate events to address this filtering need.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
pull/275/head
committed by
Jason Wang
2 changed files with 8 additions and 6 deletions
@ -1,4 +1,6 @@ |
|||
# See docs/devel/tracing.rst for syntax documentation. |
|||
|
|||
# ebpf-rss.c |
|||
ebpf_error(const char *s1, const char *s2) "error in %s: %s" |
|||
ebpf_rss_load_error(void *ctx) "ctx=%p" |
|||
ebpf_rss_mmap_error(void *ctx, const char *object) "ctx=%p object=%s" |
|||
ebpf_rss_open_error(void *ctx) "ctx=%p" |
|||
|
|||
Loading…
Reference in new issue