On 2015/07/21 13:34, Ananth N Mavinakayanahalli wrote:
On Tue, Jul 21, 2015 at 12:53:07PM +1000, Michael Ellerman wrote:
On Sun, 2015-07-19 at 11:21 +0900, Masami Hiramatsu wrote:
On 2015/07/16 19:56, Ananth N Mavinakayanahalli wrote:
Kprobes uses a breakpoint instruction to trap into
On Sun, Jul 19, 2015 at 11:21:50AM +0900, Masami Hiramatsu wrote:
On 2015/07/16 19:56, Ananth N Mavinakayanahalli wrote:
Kprobes uses a breakpoint instruction to trap into execution flow
and the probed instruction is single-stepped from an alternate location.
On some architectures like
On Sun, 2015-07-19 at 11:21 +0900, Masami Hiramatsu wrote:
On 2015/07/16 19:56, Ananth N Mavinakayanahalli wrote:
Kprobes uses a breakpoint instruction to trap into execution flow
and the probed instruction is single-stepped from an alternate location.
On some architectures like x86,
On Tue, Jul 21, 2015 at 12:53:07PM +1000, Michael Ellerman wrote:
On Sun, 2015-07-19 at 11:21 +0900, Masami Hiramatsu wrote:
On 2015/07/16 19:56, Ananth N Mavinakayanahalli wrote:
Kprobes uses a breakpoint instruction to trap into execution flow
and the probed instruction is
On 2015/07/16 19:56, Ananth N Mavinakayanahalli wrote:
Kprobes uses a breakpoint instruction to trap into execution flow
and the probed instruction is single-stepped from an alternate location.
On some architectures like x86, under certain conditions, the OPTPROBES
feature enables replacing
Kprobes uses a breakpoint instruction to trap into execution flow
and the probed instruction is single-stepped from an alternate location.
On some architectures like x86, under certain conditions, the OPTPROBES
feature enables replacing the probed instruction with a jump instead,
resulting in a
