On Sun, Jan 5, 2025 at 6:32 PM Yafang Shao <laoar.shao@xxxxxxxxx> wrote: > > On Mon, Jan 6, 2025 at 8:16 AM Alexei Starovoitov > <alexei.starovoitov@xxxxxxxxx> wrote: > > > > On Sun, Jan 5, 2025 at 4:44 AM Yafang Shao <laoar.shao@xxxxxxxxx> wrote: > > > > > > Dynamic tracepoints can be created using debugfs. For example: > > > > > > echo 'p:myprobe kernel_clone args' >> /sys/kernel/debug/tracing/kprobe_events > > > > > > This command creates a new tracepoint under debugfs: > > > > > > $ ls /sys/kernel/debug/tracing/events/kprobes/myprobe/ > > > enable filter format hist id trigger > > > > > > Although this dynamic tracepoint appears as a tracepoint, it is internally > > > implemented as a kprobe. However, it must be attached as a tracepoint to > > > function correctly in certain contexts. > > > > Nack. > > There are multiple mechanisms to create kprobe/tp via text interfaces. > > We're not going to mix them with the programmatic libbpf api. > > It appears that bpftrace still lacks support for adding a kprobe/tp > and then attaching to it directly. Is that correct? what do you mean? bpftrace supports both kprobe attaching and tp too. > What do you think about introducing this mechanism into bpftrace? With > such a feature, we could easily attach to inlined kernel functions > using bpftrace. Attaching to inlined funcs also sort-of works. It relies on dwarf, and there is work in progress to add a special section to vmlinux to annotate inlined sites, so it can work without dwarf.
