00:10 <linus2> fche: how to find all PMU name?

00:11 <linus2> such as insn["find_insns"] = @perf("find_insns")

00:11 <linus2> how to know all avaliable "find_insns"?

00:19 <linus2> it's a user defined name?

00:23 <linus2> probe perf.hw.branch_instructions.process("/usr/bin/find").counter("find_branches") {}

00:24 <linus2> how to know all avaliable perf event's style of writing perf.????.process?

00:30 <linus2> I found stap -l 'perf.*.*'

00:30 <linus2> :)

00:44 <linus2> probe perf.hw.instructions.process("/usr/bin/find").counter("find_insns") {} means get all CPUs' counter or per CPUs' counter?

00:58 <linus2> https://sourceware.org/systemtap/examples/profiling/perf.stp

00:59 <linus2> fche: when I use stap -v to run this example stp

00:59 <linus2> It errors

00:59 <linus2> semantic error: while resolving probe point: identifier 'process' at perf_find.stp:16:7

01:00 <linus2> source: probe process("/usr/bin/find").function("visit") # generally .inline'd, thus the need for debuginfo

01:00 <linus2> ^

01:00 <linus2> semantic error: no match (similar functions: _init, exit, _exit, mbsinit, _fini)

02:24 <fche> linus2, the syntax here is two-stage:

02:24 <fche> you define stap-script-level counters with the probe perf.*.counter("....") {} pseudo-probe

02:25 <fche> then use those counter names in the @perf("....") constructs in the uprobes

03:49 <linus2> May you run this code correctly? https://sourceware.org/systemtap/examples/profiling/perf.stp

11:46 <fche> hm, linus2, that stap script looks fragile w.r.t. versions of find(1), doesn't work for me on f32

11:47 <fche> hm, with debuginfo for findutils, it works better ("visit" appears to be inlined now)

11:47 <fche> but still yeah the test should be updated