From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: hw_breakpoint: fixes and improvements
Date: Thu, 25 Nov 2010 17:08:15 +0000 [thread overview]
Message-ID: <1290704899-13051-1-git-send-email-will.deacon@arm.com> (raw)
Hello,
This patch series contains a number of fixes and improvements to the
hw_breakpoint implementation for ARM. A quick summary:
* Support for cores that use the OS lock for debug register save/restore
out of reset.
* A vastly simplified alignment model to match the v7 architecture.
Breakpoints must be the same length as an instruction and be aligned
to the same boundary. Watchpoints can be 1, 2, 4 or 8 bytes long and
aligned to the appropriate datasize (byte, half-word, word, double-word).
* Minor style fix in ptrace.c
All feedback welcome!
Will Deacon (4):
ARM: hw_breakpoint: ensure OS lock is clear before writing to debug
registers
ARM: hw_breakpoint: reset control registers in hotplug path
ARM: hw_breakpoint: correct and simplify alignment fixup code
ARM: ptrace: fix style issue with hw_breakpoint interface
arch/arm/kernel/hw_breakpoint.c | 99 ++++++++++++++++++++++++++------------
arch/arm/kernel/ptrace.c | 4 +-
2 files changed, 70 insertions(+), 33 deletions(-)
next reply other threads:[~2010-11-25 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 17:08 Will Deacon [this message]
2010-11-25 17:08 ` [PATCH 1/4] ARM: hw_breakpoint: ensure OS lock is clear before writing to debug registers Will Deacon
2010-11-25 17:08 ` [PATCH 2/4] ARM: hw_breakpoint: reset control registers in hotplug path Will Deacon
2010-11-25 17:08 ` [PATCH 3/4] ARM: hw_breakpoint: correct and simplify alignment fixup code Will Deacon
2010-11-25 17:08 ` [PATCH 4/4] ARM: ptrace: fix style issue with hw_breakpoint interface Will Deacon
2010-11-27 12:39 ` [PATCH 0/4] ARM: hw_breakpoint: fixes and improvements Russell King - ARM Linux
2010-11-27 21:12 ` Will Deacon
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=1290704899-13051-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).