summaryrefslogtreecommitdiff
path: root/arch/powerpc/Kconfig.debug
diff options
context:
space:
mode:
authorRavi Bangoria <ravi.bangoria@linux.ibm.com>2020-05-14 16:47:39 +0530
committerMichael Ellerman <mpe@ellerman.id.au>2020-05-19 00:14:45 +1000
commit29da4f91c0c1fbda12b8a31be0d564930208c92e (patch)
tree5ae2bc339c5d581722f099efd4110efa05dde5be /arch/powerpc/Kconfig.debug
parent74c6881019b7d56c327fffc268d97adb5eb1b4f9 (diff)
powerpc/watchpoint: Don't allow concurrent perf and ptrace events
With Book3s DAWR, ptrace and perf watchpoints on powerpc behaves differently. Ptrace watchpoint works in one-shot mode and generates signal before executing instruction. It's ptrace user's job to single-step the instruction and re-enable the watchpoint. OTOH, in case of perf watchpoint, kernel emulates/single-steps the instruction and then generates event. If perf and ptrace creates two events with same or overlapping address ranges, it's ambiguous to decide who should single-step the instruction. Because of this issue, don't allow perf and ptrace watchpoint at the same time if their address range overlaps. Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Reviewed-by: Michael Neuling <mikey@neuling.org> Link: https://lore.kernel.org/r/20200514111741.97993-15-ravi.bangoria@linux.ibm.com
Diffstat (limited to 'arch/powerpc/Kconfig.debug')
0 files changed, 0 insertions, 0 deletions