From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM64: More flexible HW watchpoint
Date: Wed, 12 Oct 2016 11:28:02 +0530 [thread overview]
Message-ID: <cover.1476251587.git.panand@redhat.com> (raw)
Currently, we do not support all the byte select option provided by ARM64
specs for a HW watchpoint.
This patch set will help user to instrument a watchpoint with all possible
byte select options.
Pratyush Anand (4):
hw_breakpoint: Allow watchpoint of length 3,5,6 and 7
arm64: Allow hw watchpoint at varied offset from base address
arm64: Allow hw watchpoint of length 3,5,6 and 7
selftests: arm64: add test for unaligned watchpoint address handling
arch/arm64/include/asm/hw_breakpoint.h | 6 +-
arch/arm64/kernel/hw_breakpoint.c | 79 ++++++--
arch/arm64/kernel/ptrace.c | 5 +-
include/uapi/linux/hw_breakpoint.h | 4 +
tools/include/uapi/linux/hw_breakpoint.h | 4 +
tools/testing/selftests/breakpoints/Makefile | 5 +-
.../selftests/breakpoints/breakpoint_test_arm64.c | 223 +++++++++++++++++++++
7 files changed, 300 insertions(+), 26 deletions(-)
create mode 100644 tools/testing/selftests/breakpoints/breakpoint_test_arm64.c
--
2.7.4
next reply other threads:[~2016-10-12 5:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 5:58 Pratyush Anand [this message]
2016-10-12 5:58 ` [PATCH 1/4] hw_breakpoint: Allow watchpoint of length 3,5,6 and 7 Pratyush Anand
2016-10-12 5:58 ` [PATCH 2/4] arm64: Allow hw watchpoint at varied offset from base address Pratyush Anand
2016-10-12 5:58 ` [PATCH 3/4] arm64: Allow hw watchpoint of length 3,5,6 and 7 Pratyush Anand
2016-10-12 11:16 ` Yao Qi
2016-10-13 10:22 ` Pratyush Anand
2016-10-13 14:29 ` Pavel Labath
2016-10-12 5:58 ` [PATCH 4/4] selftests: arm64: add test for unaligned watchpoint address handling Pratyush Anand
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=cover.1476251587.git.panand@redhat.com \
--to=panand@redhat.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).