00:23 <fche> jhg_, hard to say under what conditions it will or won't work

00:23 <fche> stap is interpreting dwarf bytecode that a magic compiler produces for us, plus magic stack/register dumps a magic kernel gives us

00:23 <fche> so there's a lot of magic involved

00:23 <fche> and yeah sometimes we can get data for inlined functions, sometimes not

02:59 <jhg_> I turned off optimization for the kernel module that calls the kernel function. this boundary seems like it would be fairly explicit, as it is a dynamically loaded module.

03:02 <jhg_> script and output: https://hastebin.com/okexafidoh.go

03:02 <jhg_> it tracks the child by thread id

16:10 <irker882> systemtap: wcohen systemtap.git:refs/heads/master * release-3.3-68-ge180d97 / stap-exporter/scripts/example1.stp stap-exporter/scripts/example2.stp: Adjust stap-exporter probe points to work with newer Linux 4.17 kernels http://tinyurl.com/yawb5y3l

16:10 <irker882> systemtap: wcohen systemtap.git:refs/heads/master * release-3.3-69-gaa0349e / stap-exporter/scripts/cpu_throttle.stp: Correct typos in the cpu_throttle.stp comments. http://tinyurl.com/y8ojsn58

16:17 <fche> wcohen, why don't those tests use syscall.FOO aliases?

16:19 <wcohen> fche, they probably could use the non-dwarf versions of syscall.FOO

16:21 <wcohen> the probe originally using kernel.function("sys_read") changed to kernel.kprobe("sys_read") to avoid requiring kernel-debuginfo, then tweak to work with new kernels.

16:29 <irker882> systemtap: wcohen systemtap.git:refs/heads/master * release-3.3-70-g954ab72 / stap-exporter/scripts/example1.stp stap-exporter/scripts/example2.stp: Use the predefined syscall.read and syscall.open in the stap-exporter examples http://tinyurl.com/y84qjjgn

16:29 <fche> thanks

16:29 <fche> yeah the modern syscall.* aliases adapt nicely

20:41 <irker882> systemtap: wcohen systemtap.git:refs/heads/master * release-3.3-71-g3f56638 / stap-exporter/exporter.conf stap-exporter/scripts/also_ran.stp: Add the also_ran.stp script to the stap-export examples http://tinyurl.com/y8la79k8

20:42 <fche> wcohen, by the way, is there a reason these exporter samples need to be isolated from the testsuite.examples ?

20:42 <fche> ISTM they could easily be in the latter location

20:43 <fche> and stap-exporter would be configured with stap --example FOO.stp (using jafeer's recent searching mode, built with this in mind)

20:43 <wcohen> fche, certainly it would make sense to have them in testsuite.examples.

20:44 <fche> at one point the idea was not to make exporter-only-purposed scripts, but to make generally useful scripts exporter-friendly

20:52 <wcohen> fche, just put these examples in testsuite/systemtap.examples? make the scripts so they provide output both through /proc/systemtap/* and terminal? or just make people aware that the info is pulled out out of /proc/systemtap/*/...

20:52 <fche> output through both would be ideal

20:53 <fche> at probe-end if nothing else; wouldn't want to impose too frequent/high cost on an exporter-bound script in generating periodic stdout reports that are ignored

20:56 <wcohen> also how would these be grouped in testsuite/systemtap.examples? another directory for exporter-friendly scripts? or use another keyword type for "output:" of the meta data and place the scripts in the existing current directories.

20:57 <fche> suggest grouping them topically as usual

20:57 <fche> /general/ if nothing else

20:59 <wcohen> okay and have a keyword to make it easier to find the stap-exporter friendly scripts.

20:59 <fche> exactly

21:00 <fche> maybe 'prometheus'

21:00 <wcohen> okay.