fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
orivej has joined #systemtap
wcohen has joined #systemtap
CME has quit [Excess Flood]
CME has joined #systemtap
hpt has joined #systemtap
efiop has quit [Ping timeout: 240 seconds]
hkshaw has joined #systemtap
irker134 has quit [Quit: transmission timeout]
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #systemtap
_whitelogger has joined #systemtap
sanoj has joined #systemtap
zodbot has quit [Disconnected by services]
zodbot has joined #systemtap
pwithnall__ has joined #systemtap
pwithnall__ has quit [Ping timeout: 240 seconds]
baotiao has joined #systemtap
efiop has joined #systemtap
orivej has quit [Read error: Connection reset by peer]
mjw has joined #systemtap
gila has joined #systemtap
hpt has quit [Quit: Lost terminal]
orivej has joined #systemtap
scox has quit [Ping timeout: 240 seconds]
gila has quit [Remote host closed the connection]
gila has joined #systemtap
gila has quit [Client Quit]
gila has joined #systemtap
<baotiao>
where can I see the conversations log?
orivej has quit [Read error: Connection reset by peer]
orivej has joined #systemtap
orivej has quit [Ping timeout: 255 seconds]
gila has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
gromero has joined #systemtap
wcohen has quit [Ping timeout: 260 seconds]
<gromero>
Hi. I'm using systemtap to tap a function which contains a printk("HELLO"); I can see it was hit (since I see "HELLO" in dmesg) but systemtap shows nothing. Looks like that sometimes it's able to catch the function call but in some cases it just miss the call. Is that any known issue?
<baotiao>
no can you show me you probe
orivej has joined #systemtap
scox has joined #systemtap
baotiao has quit [Quit: baotiao]
orivej has quit [Ping timeout: 255 seconds]
orivej has joined #systemtap
mbenitez has joined #systemtap
mbenitez has joined #systemtap
mbenitez has quit [Changing host]
<fche>
gromero, the kernel can sometimes cause a kprobe not to fire; we usually get told of this with a 'missed probe' counter at termination
<gromero>
fche: when you say "missed probe" counter at termination, what termination you are talk about? when I hit Ctrl-C? I just see nothing: like: https://hastebin.com/raw/hicawucisi
<gromero>
fche: looks like didn't change much. I'll double check if the condition to hit load_up_fpu is indeed satisfied. ta!
hkshaw has quit [Ping timeout: 260 seconds]
<gromero>
fche: probe was not missed, indeed the condition I was looking for is dependent of a condition not always satisfied (the condition is time dependent, it has a counter that overflows from time to time)...
<gromero>
so all is fine with systemtap
<fche>
good stuff!
<gromero>
fche: heh yep :)
<fche>
by the way, on newer stap, you may not need to be so repetitious with the current_task()->foo->bar constructs all the time
<fche>
you may be able to store foo = current_task()->foo and then use foo->bar elsewhere in the script
<fche>
or that sort of thing
<fche>
or use macros
<fche>
but anyway this works too
<gromero>
fche: got it! thanks for the hint :)
gromero has quit [Remote host closed the connection]
gila has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]