From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Thomas Gleixner <tglx@kernel.org>, <catalin.marinas@arm.com>,
<will@kernel.org>, <oleg@redhat.com>, <shuah@kernel.org>,
<kees@kernel.org>, <luto@amacapital.net>, <wad@chromium.org>,
<kevin.brodsky@arm.com>, <akpm@linux-foundation.org>,
<charlie@rivosinc.com>, <ldv@strace.io>,
<anshuman.khandual@arm.com>, <mark.rutland@arm.com>,
<ryan.roberts@arm.com>, <thuth@redhat.com>, <song@kernel.org>,
<ada.coupriediaz@arm.com>, <broonie@kernel.org>,
<pengcan@kylinos.cn>, <liqiang01@kylinos.cn>, <kmal@cock.li>,
<dvyukov@google.com>, <reddybalavignesh9979@gmail.com>,
<richard.weiyang@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v12 00/13] arm64: entry: Convert to Generic Entry
Date: Wed, 4 Feb 2026 09:14:31 +0800 [thread overview]
Message-ID: <a22ccdb5-5449-5e48-790a-5c3dd0de7544@huawei.com> (raw)
In-Reply-To: <87bji552uk.ffs@tglx>
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....
Sorry for misunderstanding your v11 reply—however, these patches can
still be applied directly to the core/entry branch.
Thanks,
Jinjie
>
>
next prev parent reply other threads:[~2026-02-04 1:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 13:37 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 [this message]
2026-02-04 1:28 ` Jinjie Ruan
2026-02-04 10:39 ` Thomas Gleixner
2026-02-04 12:07 ` Will Deacon
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=a22ccdb5-5449-5e48-790a-5c3dd0de7544@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@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=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tglx@kernel.org \
--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
all inboxes | Powered by JetHome®