fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
<agentzh>
k
<irker777>
systemtap: yichun systemtap.git:master * release-4.2-109-g046b06a9e / NEWS runtime/linux/task_finder.c runtime/linux/task_finder2.c testsuite/systemtap.base/process-begin-user.exp testsuite/systemtap.base/process-begin-user_4.stp: feature: vma-related primitives now work in process.begin.
<fche>
thanks dude
<agentzh>
sure
<agentzh>
fche: i wonder if it makes sense to cache target memory via fixed number of memory pages (through LRU) to speed up target memory read intensive stap scripts.
<agentzh>
i did a simple experiment on my side and it achived 55% overall speedup for such a read-heavy scripts.
<agentzh>
*achieved
<agentzh>
my experiment was based on process_vm_readv + ptrace, it was 55% faster than the stap doing exactly the same thing against the same target process.
<agentzh>
*the stap script
<fche>
cache in what sense? we don't copy as it is
<agentzh>
fche: maybe it's just all the checks and boilerplate code around user_long_error() or other things. it's just counterintuitive that an efficient non-copying implementation of stap is so much slower than my naive ptrace-based copying implementation for the same thing.
<hassan64>
fche: So well, how to tweak it in kernel to avoid such error
<agentzh>
hassan64: maybe recompile your kernel with -Og and/or
<agentzh>
-fvar-tracking?
<agentzh>
it looks like a dwarf issue.
<agentzh>
some times we can take advantage of the ABI and access registers and stack locations directly, bypassing dwarf.
<agentzh>
$var does not always work especially when optimization is enabled.
<hassan64>
so you mean, optimization needs to be disabled
<hassan64>
Any suggestion, should I rebuild with old kernel version
<hassan64>
agentzh: Did you see it :)
<hassan64>
fche: I remember you said last week how to install systemtap 4.2. I got an error. You said, first install elfutils individual and then configure systemtap vi a./configure LDFLAGS .....
<hassan64>
sorry I forgot the step. And I missed the logs in this channel
orivej_ has quit [Ping timeout: 260 seconds]
orivej has joined #systemtap
zzhm has quit [Ping timeout: 260 seconds]
zzhm has joined #systemtap
Amy2 has joined #systemtap
Amy1 has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #systemtap
Amy2 has quit [Ping timeout: 264 seconds]
mjw has joined #systemtap
Amy2 has joined #systemtap
hpt has quit [Ping timeout: 272 seconds]
Amy2 has quit [Ping timeout: 265 seconds]
Amy2 has joined #systemtap
<fche>
hassan64, see the README file for guidance on that
<irker479>
systemtap: smakarov systemtap.git:fche/uprobes-rework * release-4.2-107-g1eaeb16df / buildrun.cxx runtime/linux/autoconf-kallsyms-on-each-symbol.c runtime/linux/kprobes.c runtime/linux/runtime.h runtime/sym.c runtime/sym.h runtime/transport/symbols.c runtime/transport/transport.c runtime/transport/transport.h runtime/transport/transport_msgs.h staprun/staprun.c translate.cxx: PR26074: pass kallsyms_lookup_name as a relocation to the
<irker479>
systemtap: yichun systemtap.git:fche/uprobes-rework * release-4.2-108-g26b24dc2e / : Bug: tapset functions reading userland registers did not work in probe process.begin
<irker479>
systemtap: yichun systemtap.git:fche/uprobes-rework * release-4.2-109-g046b06a9e / NEWS runtime/linux/task_finder.c runtime/linux/task_finder2.c testsuite/systemtap.base/process-begin-user.exp testsuite/systemtap.base/process-begin-user_4.stp: feature: vma-related primitives now work in process.begin.