All of lore.kernel.org
 help / color / mirror / Atom feed
From: dan@debian.org (Daniel Jacobowitz)
To: linux-arm-kernel@lists.infradead.org
Subject: 32-bit Thumb-2 breakpoints
Date: Thu, 28 Jan 2010 15:21:24 -0500	[thread overview]
Message-ID: <20100128202124.GA29606@caradoc.them.org> (raw)
In-Reply-To: <20100112142523.GA28804@caradoc.them.org>

On Tue, Jan 12, 2010 at 09:25:23AM -0500, Daniel Jacobowitz wrote:
> I'll plan on 0xf7f0 0xa000.

Like so.  Shall I send this to the patch system?

From: Daniel Jacobowitz <dan@codesourcery.com>

Recognize 0xf7f0 0xa000 as a 32-bit breakpoint instruction for
Thumb-2.

Signed-off-by: Daniel Jacobowitz <dan@codesourcery.com>

diff --git a/arch/arm/kernel/ptrace.c b/arch/arm/kernel/ptrace.c
index a2ea385..bd56673 100644
--- a/arch/arm/kernel/ptrace.c
+++ b/arch/arm/kernel/ptrace.c
@@ -499,10 +499,41 @@ static struct undef_hook thumb_break_hook = {
 	.fn		= break_trap,
 };
 
+static int thumb2_break_trap(struct pt_regs *regs, unsigned int instr)
+{
+	unsigned int instr2;
+	void __user *pc;
+
+	/* Check the second half of the instruction.  */
+	pc = (void __user *)(instruction_pointer(regs) + 2);
+
+	if (processor_mode(regs) == SVC_MODE) {
+		instr2 = *(u16 *) pc;
+	} else {
+		get_user(instr2, (u16 __user *)pc);
+	}
+
+	if (instr2 == 0xa000) {
+		ptrace_break(current, regs);
+		return 0;
+	} else {
+		return 1;
+	}
+}
+
+static struct undef_hook thumb2_break_hook = {
+	.instr_mask	= 0xffff,
+	.instr_val	= 0xf7f0,
+	.cpsr_mask	= PSR_T_BIT,
+	.cpsr_val	= PSR_T_BIT,
+	.fn		= thumb2_break_trap,
+};
+
 static int __init ptrace_break_init(void)
 {
 	register_undef_hook(&arm_break_hook);
 	register_undef_hook(&thumb_break_hook);
+	register_undef_hook(&thumb2_break_hook);
 	return 0;
 }
 


-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2010-01-28 20:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 21:58 32-bit Thumb-2 breakpoints Daniel Jacobowitz
2010-01-11 22:35 ` Russell King - ARM Linux
2010-01-11 22:54   ` Daniel Jacobowitz
2010-01-11 23:10     ` Jamie Lokier
2010-01-11 23:15       ` Russell King - ARM Linux
2010-01-12  0:15         ` Jamie Lokier
2010-01-11 23:17       ` Daniel Jacobowitz
2010-01-12  0:17         ` Jamie Lokier
2010-01-12  0:22           ` Daniel Jacobowitz
2010-02-03 17:23         ` Jamie Lokier
2010-02-03 17:44           ` Daniel Jacobowitz
2010-02-04 22:46             ` Pavel Machek
2010-01-11 23:31     ` Russell King - ARM Linux
2010-01-11 23:51       ` Daniel Jacobowitz
2010-01-12  9:53         ` Catalin Marinas
2010-01-12 10:34 ` Catalin Marinas
2010-01-12 14:25   ` Daniel Jacobowitz
2010-01-28 20:21     ` Daniel Jacobowitz [this message]
2010-02-02 22:43       ` Russell King - ARM Linux
2010-02-03  0:50         ` Daniel Jacobowitz
2010-02-03 11:52           ` Catalin Marinas
2010-02-03 13:28             ` Russell King - ARM Linux
2010-02-03 13:48               ` Daniel Jacobowitz
2010-02-03 14:43                 ` Russell King - ARM Linux
2010-02-03 14:56                   ` Daniel Jacobowitz
2010-02-03 13:59               ` Jamie Iles
2010-02-03 14:40                 ` Russell King - ARM Linux
2010-02-03 15:31                   ` Jamie Iles
2010-02-03 16:01                     ` Will Deacon
2010-02-03 15:02               ` Matthieu CASTET
2010-02-03 15:04                 ` Catalin Marinas
2010-02-03 15:19                   ` Nicolas Pitre
2010-02-03 15:19                 ` Daniel Jacobowitz
2010-02-03 15:30                   ` Russell King - ARM Linux
2010-02-03 15:35                     ` Daniel Jacobowitz
2010-02-03 16:35                       ` Russell King - ARM Linux
2010-02-03 17:45                         ` Daniel Jacobowitz
2010-02-03 15:35                   ` Nicolas Pitre

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=20100128202124.GA29606@caradoc.them.org \
    --to=dan@debian.org \
    --cc=linux-arm-kernel@lists.infradead.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.