[PATCH 1/2] kprobes: Update document about irq disabled state in kprobe handler
in [Kernel]
|
Prev: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
Next: [PATCH 1/5] U6/U6715 ARM architecture files
From: Masami Hiramatsu on 5 Aug 2010 08:40 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(a)hitachi.com> Cc: Ananth N Mavinakayanahalli <ananth(a)in.ibm.com> Cc: linux-kernel(a)vger.kernel.org Cc: linux-doc(a)vger.kernel.org --- Documentation/kprobes.txt | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/kprobes.txt b/Documentation/kprobes.txt index 6653017..4189f01 100644 --- a/Documentation/kprobes.txt +++ b/Documentation/kprobes.txt @@ -541,9 +541,11 @@ Kprobes does not use mutexes or allocate memory except during registration and unregistration. Probe handlers are run with preemption disabled. Depending on the -architecture, handlers may also run with interrupts disabled. In any -case, your handler should not yield the CPU (e.g., by attempting to -acquire a semaphore). +architecture and optimization state, handlers may also run with +interrupts disabled (e.g., kretprobe handlers and optimized kprobe +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 address with the trampoline's address, stack backtraces and calls -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |