Searched hist:"00 b69f1d867ddcf8884c92f5647b424088e754e4" (Results 1 – 4 of 4) sorted by relevance
| /qemu/ebpf/ |
| H A D | ebpf_rss-stub.c | 00b69f1d867ddcf8884c92f5647b424088e754e4 Wed Oct 23 08:51:00 UTC 2024 Daniel P. Berrangé <berrange@redhat.com> ebpf: add formal error reporting to all APIs
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>
Signed-off-by: Jason Wang <jasowang@redhat.com>
|
| H A D | ebpf_rss.h | 00b69f1d867ddcf8884c92f5647b424088e754e4 Wed Oct 23 08:51:00 UTC 2024 Daniel P. Berrangé <berrange@redhat.com> ebpf: add formal error reporting to all APIs
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>
Signed-off-by: Jason Wang <jasowang@redhat.com>
|
| H A D | ebpf_rss.c | 00b69f1d867ddcf8884c92f5647b424088e754e4 Wed Oct 23 08:51:00 UTC 2024 Daniel P. Berrangé <berrange@redhat.com> ebpf: add formal error reporting to all APIs
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>
Signed-off-by: Jason Wang <jasowang@redhat.com>
|
| /qemu/hw/net/ |
| H A D | virtio-net.c | 00b69f1d867ddcf8884c92f5647b424088e754e4 Wed Oct 23 08:51:00 UTC 2024 Daniel P. Berrangé <berrange@redhat.com> ebpf: add formal error reporting to all APIs
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>
Signed-off-by: Jason Wang <jasowang@redhat.com>
|