[Bug translator/23866] dissonance between kernel tracepoint parametrization, lkm vs bpf

["wcohen at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=23866

--- Comment #5 from William Cohen <wcohen at redhat dot com> ---
Created attachment 11866
  --> https://sourceware.org/bugzilla/attachment.cgi?id=11866&action=edit
WIP patch to generate raw tracepoints

This patch makes switching over to using the raw tracepoints to better match
how the traditional kernel.trace("*") works.  Really simple example:

$ sudo ../install/bin/stap -k --bpf  -m sched -e 'probe
kernel.trace("sched_switch"){printf("hello raw_trace\n");exit()}'
^CWARNING: kbuild exited with signal: 15 (Terminated)
Keeping temporary directory "/tmp/stap1oJtAx"
[wcohen@localhost systemtap]$ sudo ../install/bin/stap -v -k --bpf  -m sched -e
'probe kernel.trace("sched_switch"){printf("hello raw_trace\n");exit()}'
Pass 1: parsed user script and 50 library scripts using
250476virt/23932res/9152shr/14732data kb, in 10usr/10sys/17real ms.
Pass 2: analyzed script: 1 probe, 3 functions, 0 embeds, 0 globals using
256284virt/30968res/10176shr/20540data kb, in 65900usr/28890sys/101380real ms.
Pass 4: compiled BPF into "sched.bo" in 0usr/0sys/13real ms.
Pass 5: starting run.
hello raw_trace
Pass 5: run completed in 0usr/0sys/6real ms.
Keeping temporary directory "/tmp/stapYOYGrA"



This patch still has a number of issues that need to be addressed:

-testing whether raw tracepoints are available on the kernel
-recognizing arguments for tracepoints
-generating bpf to access those arguments

-- 
You are receiving this mail because:
You are the assignee for the bug.