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 v2 0/4] arm64: Fix single-step handling
Date: Thu, 2 Jul 2020 22:26:14 +0100 [thread overview]
Message-ID: <20200702212618.17800-1-will@kernel.org> (raw)
Hi all,
This is version two of the patches I previously posted here:
v1: https://lore.kernel.org/linux-arm-kernel/20200603151033.11512-1-will@kernel.org/
Thanks to Keno for a bunch of helpful feedback on that, which has led to
the following major changes for v2:
- Use pseudo-step traps for both entering a signal handler and exiting a
system call.
- Document our weird x7 behaviour with PTRACE_SYSCALL.
It has to be said that I'm a bit nervous about these changes. I played
around with GDB and things seemed ok, but I would really appreciate it
if Luis could run the GDB testsuite with these changes applied.
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 (4):
arm64: ptrace: Add a comment describing our syscall entry/exit trap
ABI
arm64: ptrace: Consistently use pseudo-singlestep exceptions
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/include/asm/thread_info.h | 1 +
arch/arm64/kernel/debug-monitors.c | 24 +++++++++----
arch/arm64/kernel/ptrace.c | 45 +++++++++++++++++++------
arch/arm64/kernel/signal.c | 11 ++----
arch/arm64/kernel/syscall.c | 2 +-
6 files changed, 59 insertions(+), 26 deletions(-)
--
2.27.0.212.ge8ba1cc988-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-07-02 21:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 21:26 Will Deacon [this message]
2020-07-02 21:26 ` [PATCH v2 1/4] arm64: ptrace: Add a comment describing our syscall entry/exit trap ABI Will Deacon
2020-07-02 21:26 ` Will Deacon
2020-07-02 21:26 ` [PATCH v2 2/4] arm64: ptrace: Consistently use pseudo-singlestep exceptions Will Deacon
2020-07-02 21:26 ` Will Deacon
2020-07-10 14:02 ` Sasha Levin
2020-07-10 14:02 ` Sasha Levin
2020-07-02 21:26 ` [PATCH v2 3/4] arm64: Override SPSR.SS when single-stepping is enabled Will Deacon
2020-07-02 21:26 ` Will Deacon
2020-07-10 14:02 ` Sasha Levin
2020-07-10 14:02 ` Sasha Levin
2020-07-02 21:26 ` [PATCH v2 4/4] arm64: Use test_tsk_thread_flag() for checking TIF_SINGLESTEP Will Deacon
2020-07-03 10:52 ` [PATCH v2 0/4] arm64: Fix single-step handling Luis Machado
2020-07-03 11:49 ` 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=20200702212618.17800-1-will@kernel.org \
--to=will@kernel.org \
--cc=keno@juliacomputing.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=luis.machado@linaro.org \
--cc=mark.rutland@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.