kprobes: Update document about irq disabled state in kprobe handler
Update kprobes.txt about interrupts disabled state inside kprobes handlers, because optimized probe/boosted kretprobe run without disabling interrrupts on x86. Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> Cc: Rusty Russell <rusty@rustcorp.com.au> Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com> Cc: 2nddept-manager@sdl.hitachi.co.jp LKML-Reference: <20101014031018.4100.64883.stgit@ltc236.sdl.hitachi.co.jp> Signed-off-by: Ingo Molnar <mingo@elte.hu>hifive-unleashed-5.1
parent
1efeb08d7d
commit
0f55a2f3d4
|
@ -542,9 +542,11 @@ Kprobes does not use mutexes or allocate memory except during
|
||||||
registration and unregistration.
|
registration and unregistration.
|
||||||
|
|
||||||
Probe handlers are run with preemption disabled. Depending on the
|
Probe handlers are run with preemption disabled. Depending on the
|
||||||
architecture, handlers may also run with interrupts disabled. In any
|
architecture and optimization state, handlers may also run with
|
||||||
case, your handler should not yield the CPU (e.g., by attempting to
|
interrupts disabled (e.g., kretprobe handlers and optimized kprobe
|
||||||
acquire a semaphore).
|
handlers run without interrupt disabled on x86/x86-64). In any case,
|
||||||
|
your handler should not yield the CPU (e.g., by attempting to acquire
|
||||||
|
a semaphore).
|
||||||
|
|
||||||
Since a return probe is implemented by replacing the return
|
Since a return probe is implemented by replacing the return
|
||||||
address with the trampoline's address, stack backtraces and calls
|
address with the trampoline's address, stack backtraces and calls
|
||||||
|
|
Loading…
Reference in New Issue