From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, oleg@redhat.com, tglx@linutronix.de,
peterz@infradead.org, luto@kernel.org, shuah@kernel.org,
kees@kernel.org, wad@chromium.org, kevin.brodsky@arm.com,
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,
Jinjie Ruan <ruanjinjie@huawei.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v10 00/16] arm64: entry: Convert to Generic Entry
Date: Tue, 27 Jan 2026 11:39:11 +0000 [thread overview]
Message-ID: <176951031735.722772.3896025304943173435.b4-ty@kernel.org> (raw)
In-Reply-To: <20251222114737.1334364-1-ruanjinjie@huawei.com>
On Mon, 22 Dec 2025 19:47:21 +0800, Jinjie Ruan wrote:
> Currently, x86, Riscv, Loongarch use the Generic Entry which makes
> maintainers' work easier and codes more elegant. arm64 has already
> successfully switched to the Generic IRQ Entry in commit
> b3cf07851b6c ("arm64: entry: Switch to generic IRQ entry"), it is
> time to completely convert arm64 to Generic Entry.
>
> The goal is to bring arm64 in line with other architectures that already
> use the generic entry infrastructure, reducing duplicated code and
> making it easier to share future changes in entry/exit paths, such as
> "Syscall User Dispatch".
>
> [...]
Applied first three to arm64 (for-next/entry), thanks!
[01/16] arm64: Remove unused _TIF_WORK_MASK
https://git.kernel.org/arm64/c/e7e7afdc7c14
[02/16] arm64/ptrace: Split report_syscall()
https://git.kernel.org/arm64/c/741a9000173a
[03/16] arm64/ptrace: Return early for ptrace_report_syscall_entry() error
https://git.kernel.org/arm64/c/a3386301667e
I know it's a drop in the ocean, but they look good to me and it saves
you from having to carry them over.
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-01-27 11:39 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
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 [this message]
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=176951031735.722772.3896025304943173435.b4-ty@kernel.org \
--to=will@kernel.org \
--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=kernel-team@android.com \
--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=ruanjinjie@huawei.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 \
/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