redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

kprobes/Documentation: Fix various typos 

Fix typos and clean up the wording, with the help of Randy Dunlap.

Suggested-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-arch@vger.kernel.org
Cc: linux-doc@vger.kernel.org
Link: http://lkml.kernel.org/r/20180622150740.bd26241032c972d86e23bf73@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
hifive-unleashed-5.1
Masami Hiramatsu 2018-06-22 15:07:40 +09:00 committed by Ingo Molnar
parent 0722867dcb
commit 01bdee64f9
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
Documentation/kprobes.txt
View File

@ -83,22 +83,22 @@ Execution then continues with the instruction following the probepoint.
Changing Execution Path Changing Execution Path
----------------------- -----------------------
Since the kprobes can probe into a running kernel code, it can change Since kprobes can probe into a running kernel code, it can change the
the register set, including instruction pointer. This operation register set, including instruction pointer. This operation requires
requires maximum attention, such as keeping the stack frame, recovering maximum care, such as keeping the stack frame, recovering the execution
execution path etc. Since it is operated on running kernel and need deep path etc. Since it operates on a running kernel and needs deep knowledge
knowladge of the archtecture and concurrent computing, you can easily of computer architecture and concurrent computing, you can easily shoot
shot your foot. your foot.
If you change the instruction pointer (and set up other related If you change the instruction pointer (and set up other related
registers) in pre_handler, you must return !0 so that the kprobes registers) in pre_handler, you must return !0 so that kprobes stops
stops single stepping and just returns to given address. single stepping and just returns to the given address.
This also means post_handler should not be called anymore. This also means post_handler should not be called anymore.
Note that this operation may be harder on some architectures which Note that this operation may be harder on some architectures which use
use TOC (Table of Contents) for function call, since you have to TOC (Table of Contents) for function call, since you have to setup a new
setup new TOC for your function in your module, and recover old TOC for your function in your module, and recover the old one after
one after back from it. returning from it.
Return Probes Return Probes
------------- -------------