diff options
author | Josh Stone <jistone@redhat.com> | 2009-03-09 19:12:02 -0700 |
---|---|---|
committer | Josh Stone <jistone@redhat.com> | 2009-03-09 19:24:48 -0700 |
commit | e0a17418b9d12e2a95dc345e95080ba31a41677f (patch) | |
tree | 672269fde146a3323eb5748d08707e830aeda3f5 /includes | |
parent | be184deb8fa8f58ebe693c2483b9012daff6137d (diff) | |
download | systemtap-steved-e0a17418b9d12e2a95dc345e95080ba31a41677f.tar.gz systemtap-steved-e0a17418b9d12e2a95dc345e95080ba31a41677f.tar.xz systemtap-steved-e0a17418b9d12e2a95dc345e95080ba31a41677f.zip |
Let -DINTERRUPTIBLE=0 mask interrupts in probes
Some time ago we loosened up the code for all probe types to allow
interrupts during the handler. However, when probing something like
kernel.trace("*"), you get a mix of probes in and out of the interrupt
path, and it becomes much more common to have probes skipped due to
interrupt reentrancy.
The common_probe_entryfn_prologue and common_probe_entryfn_epilogue
functions had an interruptible flag, but this was no longer used
anywhere. I removed this flag, but then reused the logic to check an
INTERRUPTIBLE macro instead. Now users can use -DINTERRUPTIBLE=0 to
prevent interrupt reentrancy in their script, at the cost of a bit more
overhead to toggle the interrupt mask.
Diffstat (limited to 'includes')
0 files changed, 0 insertions, 0 deletions