From: Will Deacon <will@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>
Cc: mark.rutland@arm.com, kees@kernel.org, catalin.marinas@arm.com,
ldv@strace.io, song@kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org, Jinjie Ruan <ruanjinjie@huawei.com>,
linux-arm-kernel@lists.infradead.org, kmal@cock.li,
thuth@redhat.com, ryan.roberts@arm.com,
anshuman.khandual@arm.com, linux-kernel@vger.kernel.org,
kevin.brodsky@arm.com, charlie@rivosinc.com, pengcan@kylinos.cn,
broonie@kernel.org, richard.weiyang@gmail.com,
dvyukov@google.com, wad@chromium.org, oleg@redhat.com,
luto@amacapital.net, liqiang01@kylinos.cn,
akpm@linux-foundation.org, reddybalavignesh9979@gmail.com
Subject: Re: [PATCH v12 00/13] arm64: entry: Convert to Generic Entry
Date: Wed, 4 Feb 2026 12:07:40 +0000 [thread overview]
Message-ID: <aYM2jM5BMRGdjnt4@willie-the-truck> (raw)
In-Reply-To: <87y0l823o9.ffs@tglx>
On Wed, Feb 04, 2026 at 11:39:34AM +0100, Thomas Gleixner wrote:
> On Wed, Feb 04 2026 at 09:28, Jinjie Ruan wrote:
> > On 2026/2/3 22:16, Thomas Gleixner wrote:
> >> On Tue, Feb 03 2026 at 21:37, 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".
> >>>
> >>> This patch set is rebased on "sched/core". And the performance
> >>
> >> Why are you using sched/core, which contains a lot of unrelated
> >> changes. core/entry is the one which has the prerequisites and nothing
> >> else....
> >
> > By the way,it looks like core/entry and arm64 for-next/entry have
> > diverged: the first three patches of this series are already in arm64
> > for-next/entry but missing from core/entry.
> > Perhaps the two branches should be reconciled so that both contain the
> > same baseline.
>
> The first three patches of this series are ARM specific and have nothing
> to do with the queued core/entry changes in tip. They are independent of
> each other and these three ARM64 changes have no business in my tree.
>
> If the ARM64 folks want to apply the rest of your series then they have
> to pull the core/entry branch into their for-next/core branch first so
> the whole thing builds.
>
> But given that the merge window opens on sunday, this is probably moot
> anyway and the rest of this series can go on top of rc1 in the ARM64
> tree w/o any further complications.
Yup, the rest of the series (beyond what we've both queued) also needs
some more review so this is all post -rc1 material.
In the meantime, thanks for picking up the generic bits.
Cheers,
Will
next prev parent reply other threads:[~2026-02-04 12:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 13:37 [PATCH v12 00/13] arm64: entry: Convert to Generic Entry Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 01/13] arm64: Remove unused _TIF_WORK_MASK Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 02/13] arm64/ptrace: Split report_syscall() Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 03/13] arm64/ptrace: Return early for ptrace_report_syscall_entry() error Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 04/13] arm64/ptrace: Refactor syscall_trace_enter/exit() Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 05/13] arm64/ptrace: Expand secure_computing() in place Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 06/13] arm64/ptrace: Use syscall_get_arguments() helper Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 07/13] arm64: ptrace: Move rseq_syscall() before audit_syscall_exit() Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 08/13] arm64: syscall: Rework el0_svc_common() Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 09/13] arm64/ptrace: Not check _TIF_SECCOMP/SYSCALL_EMU for syscall_exit_work() Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 10/13] arm64/ptrace: Do not report_syscall_exit() for PTRACE_SYSEMU_SINGLESTEP Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 11/13] arm64: entry: Convert to generic entry Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 12/13] arm64: Inline el0_svc_common() Jinjie Ruan
2026-02-03 13:37 ` [PATCH v12 13/13] selftests: sud_test: Support aarch64 Jinjie Ruan
2026-02-03 14:16 ` [PATCH v12 00/13] arm64: entry: Convert to Generic Entry Thomas Gleixner
2026-02-04 1:14 ` Jinjie Ruan
2026-02-04 1:28 ` Jinjie Ruan
2026-02-04 10:39 ` Thomas Gleixner
2026-02-04 12:07 ` Will Deacon [this message]
2026-02-05 1:20 ` Jinjie Ruan
2026-02-05 1:18 ` Jinjie Ruan
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=aYM2jM5BMRGdjnt4@willie-the-truck \
--to=will@kernel.org \
--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@amacapital.net \
--cc=mark.rutland@arm.com \
--cc=oleg@redhat.com \
--cc=pengcan@kylinos.cn \
--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@kernel.org \
--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