From: Will Deacon <will@kernel•org>
To: linux-arm-kernel@lists•infradead.org
Cc: Mark Rutland <mark.rutland@arm•com>,
kernel-team@android•com, Luis Machado <luis.machado@linaro•org>,
Will Deacon <will@kernel•org>,
Keno Fischer <keno@juliacomputing•com>
Subject: [PATCH 0/2] arm64: Fix single-stepping with reverse debugging
Date: Wed, 3 Jun 2020 16:10:31 +0100 [thread overview]
Message-ID: <20200603151033.11512-1-will@kernel.org> (raw)
Hi all,
This series fixes a bug in our hardware single-step and ptrace logic that
was reported by Luis after seeing some GDB testsuite failures. The second
patch is cosmetic, but I was in the area.
Cheers,
Will
Cc: <kernel-team@android•com>
Cc: Mark Rutland <mark.rutland@arm•com>
Cc: Luis Machado <luis.machado@linaro•org>
Cc: Keno Fischer <keno@juliacomputing•com>
--->8
Will Deacon (2):
arm64: Override SPSR.SS when single-stepping is enabled
arm64: Use test_tsk_thread_flag() for checking TIF_SINGLESTEP
arch/arm64/include/asm/debug-monitors.h | 2 ++
arch/arm64/kernel/debug-monitors.c | 24 ++++++++++++++++++------
arch/arm64/kernel/ptrace.c | 4 ++--
arch/arm64/kernel/signal.c | 6 +++++-
4 files changed, 27 insertions(+), 9 deletions(-)
--
2.27.0.rc2.251.g90737beb825-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-06-03 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 15:10 Will Deacon [this message]
2020-06-03 15:10 ` [PATCH 1/2] arm64: Override SPSR.SS when single-stepping is enabled Will Deacon
2020-06-03 15:42 ` Keno Fischer
2020-06-03 15:53 ` Will Deacon
2020-06-03 16:56 ` Keno Fischer
2020-06-04 8:32 ` Will Deacon
2020-06-04 22:32 ` Keno Fischer
2020-06-05 4:50 ` Luis Machado
2020-06-05 20:12 ` Keno Fischer
2020-06-03 15:10 ` [PATCH 2/2] arm64: Use test_tsk_thread_flag() for checking TIF_SINGLESTEP 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=20200603151033.11512-1-will@kernel.org \
--to=will@kernel$(echo .)org \
--cc=keno@juliacomputing$(echo .)com \
--cc=kernel-team@android$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=luis.machado@linaro$(echo .)org \
--cc=mark.rutland@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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