You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ktrace currently instruments all locations for a specific run using either only kprobes or kfuncs (fentry).
Check multi probe type (should be similar to SystemTap).
Add support for automated selection of the best probe type.
This will likely require some evaluation of probe type runtime or attachment overhead etc.
Add support for mixing different probe types in a single BPF program, e.g., for situations when kfunc does not support a particular location but kprobe does.
Consider adding support for uprobes as well, so we can get more precise traces originating from the benchmark itself.
There might be an issue with using kfunc (despite listed for kfunc) and it might fail on bpf-attachment/loading.
The text was updated successfully, but these errors were encountered:
Ktrace currently instruments all locations for a specific run using either only kprobes or kfuncs (fentry).
There might be an issue with using kfunc (despite listed for kfunc) and it might fail on bpf-attachment/loading.
The text was updated successfully, but these errors were encountered: