From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL][RESEND] ARM: hw_breakpoint: fixes and improvements
Date: Fri, 17 Dec 2010 16:24:39 -0000 [thread overview]
Message-ID: <000b01cb9e06$e75104b0$b5f30e10$@deacon@arm.com> (raw)
Hi Russell,
I don't think you've pulled this yet, but I've been having
issues with my git server so here's a mirrored address which
is up-to-date. Note that I've made some minor changes to the
final patch since the last pull request.
I'm on holiday from today so if you have any problems, I'll
resolve them in the new year.
Cheers,
Will
The following changes since commit e8a7e48bb248a1196484d3f8afa53bded2b24e71:
Linus Torvalds (1):
Linux 2.6.37-rc4
are available in the git repository at:
git://repo.or.cz/linux-2.6/linux-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 | 543 ++++++++++++++++++++--------------
arch/arm/kernel/ptrace.c | 4 +-
5 files changed, 346 insertions(+), 228 deletions(-)
reply other threads:[~2010-12-17 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000b01cb9e06$e75104b0$b5f30e10$@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).