From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: hw_breakpoint: fixes and improvements
Date: Mon, 6 Dec 2010 16:59:11 -0000 [thread overview]
Message-ID: <007001cb9566$e84d3d50$b8e7b7f0$@deacon@arm.com> (raw)
Hi Russell,
Please pull these hw_breakpoint patches, they address a number
of issues and corner-cases with the current implementation.
Thanks,
Will
The following changes since commit e8a7e48bb248a1196484d3f8afa53bded2b24e71:
Linus Torvalds (1):
Linux 2.6.37-rc4
are available in the git repository at:
git://linux-arm.org/linux-2.6-wd.git hw-breakpoint
Will Deacon (11):
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: hw_breakpoint: disable preemption during debug exception handling
ARM: hw_breakpoint: don't advertise reserved breakpoints
ARM: hw_breakpoint: do not allocate new breakpoints with preemption disabled
ARM: hw_breakpoint: unify single-stepping code for watchpoints and breakpoints
ARM: hw_breakpoint: disallow per-cpu breakpoints without overflow handler
ARM: ptrace: fix style issue with hw_breakpoint interface
ARM: hw_breakpoint: fix warnings generated by sparse
ARM: hw_breakpoint: do not fail initcall if monitor mode is disabled
arch/arm/include/asm/hw_breakpoint.h | 4 +-
arch/arm/kernel/entry-armv.S | 4 +
arch/arm/kernel/entry-header.S | 19 ++
arch/arm/kernel/hw_breakpoint.c | 551 ++++++++++++++++++++--------------
arch/arm/kernel/ptrace.c | 4 +-
5 files changed, 354 insertions(+), 228 deletions(-)
next reply other threads:[~2010-12-06 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 16:59 Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-10 10:31 [GIT PULL] ARM: hw_breakpoint: fixes and improvements 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='007001cb9566$e84d3d50$b8e7b7f0$@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).