fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
jhg_ has quit [Read error: Connection reset by peer]
_whitelogger has joined #systemtap
slowfranklin has joined #systemtap
pwithnall has joined #systemtap
pwithnall has quit [Ping timeout: 240 seconds]
pwithnall has joined #systemtap
pwithnall has quit [Quit: pwithnall]
gila has quit [Ping timeout: 260 seconds]
pwithnall has joined #systemtap
gila has joined #systemtap
orivej has joined #systemtap
mjw has joined #systemtap
orivej has quit [Ping timeout: 252 seconds]
orivej has joined #systemtap
brolley has joined #systemtap
brolley has quit [Ping timeout: 272 seconds]
brolley has joined #systemtap
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #systemtap
tromey has joined #systemtap
slowfranklin has quit [Quit: slowfranklin]
brolley has quit [Ping timeout: 252 seconds]
brolley has joined #systemtap
mjw has quit [Quit: Leaving]
pwithnall has quit [Quit: pwithnall]
tromey has quit [Quit: ERC (IRC client for Emacs 26.1.50)]
<fche>
haven't had any new thoughts about the @vma() one ... do you have a sense of whether there is any conceivable safety (crashability) hazard with it?
<agentzh>
not any that i'm aware of. it's just converting integer values itself, not accessing any memory.
<agentzh>
*any target memory
<fche>
no 0-dereference type of possibilities?
<agentzh>
nope
<agentzh>
it's just integer additions (in case of PIC/PIE).
<agentzh>
or no-op for non-PIC/PIE cases.
<agentzh>
fche: out of curiosity, are you guys using virtualization solutions like qemu to debug weird kernel-space issues?
<fche>
all the time
<agentzh>
nice.
<agentzh>
with kvm?
<fche>
but haven't had any crashes in quite some time, so am running tests on my main workstation much fo the time
<fche>
yeah kvm is a favorite
<agentzh>
i'm still thinking about that CPU lockup issue while running the stap test suite with high job count.
<agentzh>
it worries me.
<fche>
yeah
<agentzh>
do you also try vbox?
<agentzh>
virtualbox i mean
<fche>
nope
<agentzh>
too big? ;)
<fche>
hm that rings a bell, with some virtualization engines, kernel kprobes don't work as reliably as with others
<agentzh>
or too oracle?
<fche>
or at least didn't in the past
<agentzh>
oh, so it might be something specific to vmware?
<fche>
possible
<agentzh>
i was using vmware.
<agentzh>
if it's indeed the case, then it would be quite relieving.
<agentzh>
few people run vmware for production anyway.
<agentzh>
fche: do you have any detailed info on the kprobes instabilities on certain virt engines?
<agentzh>
that would be very helpful for me.
<fche>
sorry, nothing recent
<agentzh>
okay, np.
<fche>
but ISTR kprobes on large-smp boxes were implicated
<fche>
so probably some sort of icache flushing matter. .... dunno sorry
<agentzh>
i'll make note anyway. thanks.
<agentzh>
maybe i should start by attempts of reproducing the issue on bare metals.