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 4/4] arm64: Use test_tsk_thread_flag() for checking TIF_SINGLESTEP
Date: Thu, 2 Jul 2020 22:26:18 +0100 [thread overview]
Message-ID: <20200702212618.17800-5-will@kernel.org> (raw)
In-Reply-To: <20200702212618.17800-1-will@kernel.org>
Rather than open-code test_tsk_thread_flag() at each callsite, simply
replace the couple of offenders with calls to test_tsk_thread_flag()
directly.
Signed-off-by: Will Deacon <will@kernel.org>
---
arch/arm64/kernel/debug-monitors.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/kernel/debug-monitors.c b/arch/arm64/kernel/debug-monitors.c
index 91146c0a3691..7310a4f7f993 100644
--- a/arch/arm64/kernel/debug-monitors.c
+++ b/arch/arm64/kernel/debug-monitors.c
@@ -394,14 +394,14 @@ void user_rewind_single_step(struct task_struct *task)
* If single step is active for this thread, then set SPSR.SS
* to 1 to avoid returning to the active-pending state.
*/
- if (test_ti_thread_flag(task_thread_info(task), TIF_SINGLESTEP))
+ if (test_tsk_thread_flag(task, TIF_SINGLESTEP))
set_regs_spsr_ss(task_pt_regs(task));
}
NOKPROBE_SYMBOL(user_rewind_single_step);
void user_fastforward_single_step(struct task_struct *task)
{
- if (test_ti_thread_flag(task_thread_info(task), TIF_SINGLESTEP))
+ if (test_tsk_thread_flag(task, TIF_SINGLESTEP))
clear_regs_spsr_ss(task_pt_regs(task));
}
--
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 prev parent reply other threads:[~2020-07-02 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 21:26 [PATCH v2 0/4] arm64: Fix single-step handling Will Deacon
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 ` [PATCH v2 2/4] arm64: ptrace: Consistently use pseudo-singlestep exceptions Will Deacon
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-10 14:02 ` Sasha Levin
2020-07-02 21:26 ` Will Deacon [this message]
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-5-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 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).