19:21 <irker116> systemtap: wcohen systemtap.git:master * release-4.4-143-g6d9867db5 / testsuite/systemtap.examples/io/deviceseeks.stp testsuite/systemtap.examples/process/schedtimes.stp: Adjust deviceseeks.stp to work with newer kernels

19:48 <kerneltoast> fche, i'm seeing a lot of interned strings inside of the stap c++ code, and some of them have been interned for over a decade

19:48 <kerneltoast> when will they be offered a full time job?

19:48 <fche> age 18

19:49 <kerneltoast> i can't help but think that they'll defect to the competition at 18

19:50 <kerneltoast> they might become an ebpf helper or manager

20:21 <kerneltoast> fche, where's the builder for `process("a.out").function("bonjour")`

20:21 <kerneltoast> i don't see any `bind_str(TOK_PROCESS)->bind_str(TOK_FUNCTION)`

20:22 <fche> they are probably a function apart

20:22 <fche> since process() has a couple of variants , CARTESIAN PRODUCT function etc.

20:22 <kerneltoast> whaddya mean

20:23 <kerneltoast> i'm just grepping for `bind_str(TOK_FUNCTION)` and i don't see any `bind_str(TOK_PROCESS)` before it

20:23 <fche> correct

20:24 <fche> dwarf_derived_probe::register_patterns

20:25 <kerneltoast> ah, that thing

20:28 <fche> so don't modify that, but can copy the uprobes[] array, then generate the .data() bits as a suffix

20:28 <fche> or whatever

20:29 <kerneltoast> i've got my process path/pid parsed but i dunno where to plumb it into task finder

20:30 <kerneltoast> https://paste.centos.org/view/39c30637

20:30 <fche> maybe look at how the tapset-perfmon* does it

20:31 <fche> yeah that's a start

20:31 <fche> you need to plumb it into a task-finder config to have it identify target processes at run time

20:31 <fche> and you need to plumb those callbacks into the kernel api for userspace data watchpoints

20:32 <fche> and the callbacks from that back into the compiled probes

20:32 <fche> yeah maybe tapset-perfmon* a good model

20:34 <kerneltoast> https://usercontent.irccloud-cdn.com/file/4BcxwY11/plumb.png