From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Kevin Brodsky <kevin.brodsky@arm.com>, <catalin.marinas@arm.com>,
<will@kernel.org>, <oleg@redhat.com>, <tglx@linutronix.de>,
<peterz@infradead.org>, <luto@kernel.org>, <shuah@kernel.org>,
<kees@kernel.org>, <wad@chromium.org>, <macro@orcam.me.uk>,
<charlie@rivosinc.com>, <akpm@linux-foundation.org>,
<ldv@strace.io>, <anshuman.khandual@arm.com>,
<mark.rutland@arm.com>, <thuth@redhat.com>, <song@kernel.org>,
<ryan.roberts@arm.com>, <ada.coupriediaz@arm.com>,
<broonie@kernel.org>, <liqiang01@kylinos.cn>,
<pengcan@kylinos.cn>, <kmal@cock.li>, <dvyukov@google.com>,
<richard.weiyang@gmail.com>, <reddybalavignesh9979@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v10 11/16] entry: Split syscall_exit_to_user_mode_work() for arch reuse
Date: Wed, 31 Dec 2025 09:35:03 +0800 [thread overview]
Message-ID: <d55de365-b246-32ed-14eb-1ea0318794a5@huawei.com> (raw)
In-Reply-To: <f3c32e7f-f940-4cb0-941c-cb7f7f628d88@arm.com>
On 2025/12/30 2:03, Kevin Brodsky wrote:
> On 22/12/2025 12:47, Jinjie Ruan wrote:
>> In the generic entry code, the beginning of
>> syscall_exit_to_user_mode_work() can be reused on arm64 so it makes
>> sense to split it.
>>
>> In preparation for moving arm64 over to the generic entry
>> code, split out syscall_exit_to_user_mode_work_prepare() helper from
>> syscall_exit_to_user_mode_work().
>>
>> No functional changes.
>>
>> Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com>
>> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
>> ---
>> include/linux/entry-common.h | 35 ++++++++++++++++++++++-------------
>> 1 file changed, 22 insertions(+), 13 deletions(-)
>>
>> diff --git a/include/linux/entry-common.h b/include/linux/entry-common.h
>> index 87efb38b7081..0de0e60630e1 100644
>> --- a/include/linux/entry-common.h
>> +++ b/include/linux/entry-common.h
>> @@ -121,20 +121,11 @@ static __always_inline long syscall_enter_from_user_mode(struct pt_regs *regs, l
>> */
>> void syscall_exit_work(struct pt_regs *regs, unsigned long work);
>>
>> -/**
>> - * syscall_exit_to_user_mode_work - Handle work before returning to user mode
>> - * @regs: Pointer to currents pt_regs
>> - *
>> - * Same as step 1 and 2 of syscall_exit_to_user_mode() but without calling
>> - * exit_to_user_mode() to perform the final transition to user mode.
>> - *
>> - * Calling convention is the same as for syscall_exit_to_user_mode() and it
>> - * returns with all work handled and interrupts disabled. The caller must
>> - * invoke exit_to_user_mode() before actually switching to user mode to
>> - * make the final state transitions. Interrupts must stay disabled between
>> - * return from this function and the invocation of exit_to_user_mode().
>> +/*
>> + * Syscall specific exit to user mode preparation. Runs with interrupts
>> + * enabled.
>> */
>> -static __always_inline void syscall_exit_to_user_mode_work(struct pt_regs *regs)
>> +static __always_inline void syscall_exit_to_user_mode_work_prepare(struct pt_regs *regs)
>> {
>> unsigned long work = READ_ONCE(current_thread_info()->syscall_work);
>> unsigned long nr = syscall_get_nr(current, regs);
>> @@ -155,6 +146,24 @@ static __always_inline void syscall_exit_to_user_mode_work(struct pt_regs *regs)
>> */
>> if (unlikely(work & SYSCALL_WORK_EXIT))
>> syscall_exit_work(regs, work);
>> +}
>> +
>> +/**
>> + * syscall_exit_to_user_mode_work - Handle work before returning to user mode
>> + * @regs: Pointer to currents pt_regs
>> + *
>> + * Same as step 1 and 2 of syscall_exit_to_user_mode() but without calling
>> + * exit_to_user_mode() to perform the final transition to user mode.
>> + *
>> + * Calling convention is the same as for syscall_exit_to_user_mode() and it
>> + * returns with all work handled and interrupts disabled. The caller must
>> + * invoke exit_to_user_mode() before actually switching to user mode to
>> + * make the final state transitions. Interrupts must stay disabled between
>> + * return from this function and the invocation of exit_to_user_mode().
>> + */
>> +static __always_inline void syscall_exit_to_user_mode_work(struct pt_regs *regs)
>> +{
>> + syscall_exit_to_user_mode_work_prepare(regs);
>
> The naming is getting awfully confusing, with the separate introduction
> of syscall_exit_to_user_mode_prepare().
>
> Having had a closer look, do we really need
> syscall_exit_to_user_mode_work() as it currently stands? Nothing calls
> it except the generic syscall_exit_to_user_mode(). Which makes me think:
> how about moving the two lines below into syscall_exit_to_user_mode()
> instead of creating a new helper? IOW:
It looks fine to me, this will make the change less. The comment also
need to be updated.
>
> @@ -155,8 +155,6 @@ static __always_inline void
> syscall_exit_to_user_mode_work(struct pt_regs *regs)
> */
> if (unlikely(work & SYSCALL_WORK_EXIT))
> syscall_exit_work(regs, work);
> - local_irq_disable_exit_to_user();
> - syscall_exit_to_user_mode_prepare(regs);
> }
>
> /**
> @@ -192,6 +190,8 @@ static __always_inline void
> syscall_exit_to_user_mode(struct pt_regs *regs)
> {
> instrumentation_begin();
> syscall_exit_to_user_mode_work(regs);
> + local_irq_disable_exit_to_user();
> + syscall_exit_to_user_mode_prepare(regs);
> instrumentation_end();
> exit_to_user_mode();
> }
>
> - Kevin
>
>> local_irq_disable_exit_to_user();
>> syscall_exit_to_user_mode_prepare(regs);
>> }
>
next prev parent reply other threads:[~2025-12-31 1:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 11:47 [PATCH v10 00/16] arm64: entry: Convert to Generic Entry Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 01/16] arm64: Remove unused _TIF_WORK_MASK Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 02/16] arm64/ptrace: Split report_syscall() Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 03/16] arm64/ptrace: Return early for ptrace_report_syscall_entry() error Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 04/16] arm64/ptrace: Refactor syscall_trace_enter/exit() Jinjie Ruan
2026-01-26 16:42 ` Will Deacon
2026-01-27 3:01 ` Jinjie Ruan
2026-01-27 9:43 ` Kevin Brodsky
2026-01-27 11:02 ` Jinjie Ruan
2026-01-27 14:54 ` Kevin Brodsky
2025-12-22 11:47 ` [PATCH v10 05/16] arm64: ptrace: Move rseq_syscall() before audit_syscall_exit() Jinjie Ruan
2026-01-26 19:02 ` Will Deacon
2026-01-27 9:44 ` Kevin Brodsky
2026-01-27 11:34 ` Jinjie Ruan
2026-01-27 15:06 ` Kevin Brodsky
2026-01-28 1:09 ` Jinjie Ruan
2026-01-28 14:53 ` Kevin Brodsky
2026-01-29 3:50 ` Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 06/16] arm64: syscall: Rework el0_svc_common() Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 07/16] arm64/ptrace: Not check _TIF_SECCOMP/SYSCALL_EMU for syscall_exit_work() Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 08/16] arm64/ptrace: Do not report_syscall_exit() for PTRACE_SYSEMU_SINGLESTEP Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 09/16] arm64/ptrace: Expand secure_computing() in place Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 10/16] arm64/ptrace: Use syscall_get_arguments() helper Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 11/16] entry: Split syscall_exit_to_user_mode_work() for arch reuse Jinjie Ruan
2025-12-29 18:03 ` Kevin Brodsky
2025-12-31 1:35 ` Jinjie Ruan [this message]
2025-12-22 11:47 ` [PATCH v10 12/16] entry: Add arch_ptrace_report_syscall_entry/exit() Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 13/16] arm64: entry: Convert to generic entry Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 14/16] arm64: Inline el0_svc_common() Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 15/16] entry: Inline syscall_exit_work() and syscall_trace_enter() Jinjie Ruan
2025-12-22 11:47 ` [PATCH v10 16/16] selftests: sud_test: Support aarch64 Jinjie Ruan
2026-01-19 2:02 ` [PATCH v10 00/16] arm64: entry: Convert to Generic Entry Jinjie Ruan
2026-01-27 11:39 ` 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=d55de365-b246-32ed-14eb-1ea0318794a5@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=ada.coupriediaz@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=charlie@rivosinc.com \
--cc=dvyukov@google.com \
--cc=kees@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=kmal@cock.li \
--cc=ldv@strace.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liqiang01@kylinos.cn \
--cc=luto@kernel.org \
--cc=macro@orcam.me.uk \
--cc=mark.rutland@arm.com \
--cc=oleg@redhat.com \
--cc=pengcan@kylinos.cn \
--cc=peterz@infradead.org \
--cc=reddybalavignesh9979@gmail.com \
--cc=richard.weiyang@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=thuth@redhat.com \
--cc=wad@chromium.org \
--cc=will@kernel.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