summaryrefslogtreecommitdiff
path: root/Documentation/powerpc/ptrace.txt
diff options
context:
space:
mode:
authorMichael Neuling <mikey@neuling.org>2013-03-21 20:12:33 +0000
committerMichael Ellerman <michael@ellerman.id.au>2013-04-18 15:59:55 +1000
commit517b7314770c9247ed77bc0591dbeb362603a371 (patch)
treeb5306df74c471c66598922a4baaca75540526d29 /Documentation/powerpc/ptrace.txt
parenta6a058e52a0ce62de84496c9d4b133f2afc61f27 (diff)
powerpc/ptrace: Add DAWR debug feature info for userspace
This adds new debug feature information so that the DAWR can be identified by userspace tools like GDB. Unfortunately the DAWR doesn't sit nicely into the current description that ptrace provides to userspace via struct ppc_debug_info. It doesn't allow for specifying that only some ranges are possible or even the end alignment constraints (DAWR only allows 512 byte wide ranges which can't cross a 512 byte boundary). After talking to Edjunior Machado (GDB ppc developer), it was decided this was the best approach. Just mark it as debug feature DAWR and tools like GDB can internally decide the constraints. Signed-off-by: Michael Neuling <mikey@neuling.org> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Diffstat (limited to 'Documentation/powerpc/ptrace.txt')
-rw-r--r--Documentation/powerpc/ptrace.txt1
1 files changed, 1 insertions, 0 deletions
diff --git a/Documentation/powerpc/ptrace.txt b/Documentation/powerpc/ptrace.txt
index f2a7a3919772..99c5ce88d0fe 100644
--- a/Documentation/powerpc/ptrace.txt
+++ b/Documentation/powerpc/ptrace.txt
@@ -40,6 +40,7 @@ features will have bits indicating whether there is support for:
#define PPC_DEBUG_FEATURE_INSN_BP_MASK 0x2
#define PPC_DEBUG_FEATURE_DATA_BP_RANGE 0x4
#define PPC_DEBUG_FEATURE_DATA_BP_MASK 0x8
+#define PPC_DEBUG_FEATURE_DATA_BP_DAWR 0x10
2. PTRACE_SETHWDEBUG