From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM64: Fix irq generation between breakpoint and step exception
Date: Tue, 4 Jul 2017 00:40:25 +0530 [thread overview]
Message-ID: <cover.1499107909.git.panand@redhat.com> (raw)
samples/hw_breakpoint/data_breakpoint.c passes with x86_64 but fails with
ARM64. Even though it has been NAKed previously on upstream [1, 2], I have
tried to come up with patches which can resolve it for ARM64 as well.
I noticed that even perf step exception can go into an infinite loop if CPU
receives an interrupt while executing breakpoint/watchpoint handler. So,
event though we are not concerned about above test, we will have to find a
solution for the perf issue.
This patchset attempts to resolve both the issue. Please review.
[1] http://marc.info/?l=linux-arm-kernel&m=149580777524910&w=2
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-April/425266.html
Pratyush Anand (2):
arm64: hw_breakpoint: Allow stepping if a kernel mode overflow handler
exists
arm64: disable irq between breakpoint and step exception
arch/arm64/kernel/debug-monitors.c | 3 +++
arch/arm64/kernel/hw_breakpoint.c | 13 ++++++++-----
arch/arm64/mm/fault.c | 22 ++++++++++++++++++----
3 files changed, 29 insertions(+), 9 deletions(-)
--
2.9.3
next reply other threads:[~2017-07-03 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 19:10 Pratyush Anand [this message]
2017-07-03 19:10 ` [PATCH 1/2] arm64: hw_breakpoint: Allow stepping if a kernel mode overflow handler exists Pratyush Anand
2017-07-04 9:40 ` Mark Rutland
2017-07-04 10:01 ` Pratyush Anand
2017-07-03 19:10 ` [PATCH 2/2] arm64: disable irq between breakpoint and step exception 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.1499107909.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).