From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
dwg@au1.ibm.com
Subject: [PATCH 2/2] [PowerPC Book3E] Introduce new ptrace debug feature flag
Date: Fri, 19 Aug 2011 13:23:38 +0530 [thread overview]
Message-ID: <20110819075338.GC21817@in.ibm.com> (raw)
In-Reply-To: <20110819074527.GA21817@in.ibm.com>
While PPC_PTRACE_SETHWDEBUG ptrace flag in PowerPC accepts
PPC_BREAKPOINT_MODE_EXACT mode of breakpoint, the same is not intimated to the
user-space debuggers (like GDB) who may want to use it. Hence we introduce a
new PPC_DEBUG_FEATURE_DATA_BP_EXACT flag which will be populated on the
"features" member of "struct ppc_debug_info" to advertise support for the
same on Book3E PowerPC processors.
Signed-off-by: K.Prasad <prasad@linux.vnet.ibm.com>
---
arch/powerpc/include/asm/ptrace.h | 1 +
arch/powerpc/kernel/ptrace.c | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/include/asm/ptrace.h b/arch/powerpc/include/asm/ptrace.h
index 48223f9..cf014f9 100644
--- a/arch/powerpc/include/asm/ptrace.h
+++ b/arch/powerpc/include/asm/ptrace.h
@@ -380,6 +380,7 @@ struct ppc_debug_info {
#define PPC_DEBUG_FEATURE_INSN_BP_MASK 0x0000000000000002
#define PPC_DEBUG_FEATURE_DATA_BP_RANGE 0x0000000000000004
#define PPC_DEBUG_FEATURE_DATA_BP_MASK 0x0000000000000008
+#define PPC_DEBUG_FEATURE_DATA_BP_EXACT 0x0000000000000010
#ifndef __ASSEMBLY__
diff --git a/arch/powerpc/kernel/ptrace.c b/arch/powerpc/kernel/ptrace.c
index 18d28b6..71db5a6 100644
--- a/arch/powerpc/kernel/ptrace.c
+++ b/arch/powerpc/kernel/ptrace.c
@@ -1636,6 +1636,7 @@ long arch_ptrace(struct task_struct *child, long request,
#ifdef CONFIG_PPC_ADV_DEBUG_DAC_RANGE
dbginfo.features |=
PPC_DEBUG_FEATURE_DATA_BP_RANGE |
+ PPC_DEBUG_FEATURE_DATA_BP_EXACT |
PPC_DEBUG_FEATURE_DATA_BP_MASK;
#endif
#else /* !CONFIG_PPC_ADV_DEBUG_REGS */
--
1.7.4.1
next prev parent reply other threads:[~2011-08-19 7:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 7:45 [PATCH 0/2] Changes to PowerPC ptrace flags using watchpoints K.Prasad
2011-08-19 7:51 ` [PATCH 1/2] [hw-breakpoint] Use generic hw-breakpoint interfaces for new PPC ptrace flags K.Prasad
2011-08-23 5:08 ` David Gibson
2011-08-23 9:25 ` K.Prasad
2011-08-24 3:59 ` David Gibson
2011-08-26 9:35 ` K.Prasad
2011-09-16 7:27 ` K.Prasad
2011-10-12 3:33 ` David Gibson
2011-10-12 17:39 ` K.Prasad
2011-11-28 3:11 ` David Gibson
2011-12-01 10:20 ` K.Prasad
2011-12-07 19:01 ` Thiago Jung Bauermann
2011-12-08 8:30 ` K.Prasad
2011-08-19 7:53 ` K.Prasad [this message]
2011-08-23 5:09 ` [PATCH 2/2] [PowerPC Book3E] Introduce new ptrace debug feature flag David Gibson
2011-08-23 9:27 ` K.Prasad
2011-08-24 4:00 ` David Gibson
2011-08-25 0:41 ` Thiago Jung Bauermann
2011-08-26 4:41 ` David Gibson
2011-08-31 0:27 ` Thiago Jung Bauermann
2011-09-19 1:10 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2011-12-08 11:12 [PATCH 0/2] Changes to PowerPC ptrace flags using watchpoints - v2 K.Prasad
2011-12-08 11:23 ` [PATCH 2/2] [PowerPC Book3E] Introduce new ptrace debug feature flag K.Prasad
2011-12-21 0:55 ` David Gibson
2011-12-22 9:34 ` K.Prasad
2012-01-16 8:18 ` David Gibson
2012-02-15 22:18 ` Thiago Jung Bauermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110819075338.GC21817@in.ibm.com \
--to=prasad@linux.vnet.ibm.com \
--cc=bauerman@br.ibm.com \
--cc=dwg@au1.ibm.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.