From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Linus Walleij <linusw@kernel.org>
Cc: <catalin.marinas@arm.com>, <will@kernel.org>,
<mark.rutland@arm.com>, <oleg@redhat.com>, <shuah@kernel.org>,
<kees@kernel.org>, <luto@amacapital.net>, <wad@chromium.org>,
<peterz@infradead.org>, <ada.coupriediaz@arm.com>,
<kevin.brodsky@arm.com>, <yeoreum.yun@arm.com>,
<james.morse@arm.com>, <thuth@redhat.com>, <tglx@kernel.org>,
<vladimir.murzin@arm.com>, <broonie@kernel.org>,
<ryan.roberts@arm.com>, <liqiang01@kylinos.cn>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v20 00/15] arm64: entry: Convert to Generic Entry
Date: Thu, 5 Nov 2026 15:49:26 +0800 [thread overview]
Message-ID: <4831fb24-85f2-4273-9cf8-9ac60dd6555f@huawei.com> (raw)
In-Reply-To: <CAD++jLnX2ptZnOHWvU6QR+4VKeM+kPfjShkB0DQZpr3hnG0DOQ@mail.gmail.com>
在 2026/11/4 21:38, Linus Walleij 写道:
> On Mon, Oct 26, 2026 at 9:52 AM Jinjie Ruan <ruanjinjie@huawei.com> wrote:
>
>> Hi Mark and all,
>>
>> Ping.
>>
>> Are there any further review comments or new suggestions for changes?
>> I’m happy to address anything that comes up.
>
> You're pinging in the middle of the merge window, people are busy!
Hi Linus,
Sorry for pinging during the merge window.
>
> Now that v7.4-rc1 is out, rebase on v7.4-rc1 and resend please.
No problem. Will rebase on v7.4-rc1, retest and resend. Thank you!
>
> Sorry that this requires constant rebasing and resending, generic
> entry is so intrusive that we need to take baby steps... maybe we
System calls path seem to be more deterministic than the interrupt path.
However, considering that arm64 is widely used and this is in a critical
system path, it is indeed necessary to think twice before proceeding.
> can merge some of the patches and not yet all? I.e. a trickle-in
> method?
Ensure there are no functional changes, a trickle-in works for me.
And it may give me more confidence to move forward 😂
>
> Yours,
> Linus Walleij
--
Best regards,
Jinjie
prev parent reply other threads:[~2026-11-05 7:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 10:17 Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 01/15] arm64: ptrace: Drop redundant pseudo-single-step for SYSEMU_SINGLESTEP Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 02/15] arm64: ptrace: Rework audit_syscall_entry() Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 03/15] arm64: ptrace: Open-code seccomp check in syscall_trace_enter() Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 04/15] arm64: ptrace: Rename and clean up syscall_trace_enter() Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 05/15] arm64: ptrace: Protect rseq_syscall() from tracer PC modifications Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 06/15] arm64: syscall: Rework the syscall exit path in el0_svc_common() Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 07/15] arm64: ptrace: Pass thread flags to trace enter/exit Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 08/15] arm64: ptrace: Extract arm64_syscall_exit_to_user_mode_work() helper Jinjie Ruan
2026-09-30 10:17 ` [PATCH v20 09/15] arm64: ptrace: Align syscall exit work semantics with generic entry Jinjie Ruan
2026-09-30 10:18 ` [PATCH v20 10/15] arm64: syscall: Use exit-specific flags check in el0_svc_common() Jinjie Ruan
2026-09-30 10:18 ` [PATCH v20 11/15] arm64: syscall: Simplify el0_svc_common() syscall exit path Jinjie Ruan
2026-09-30 10:18 ` [PATCH v20 12/15] arm64: ptrace: Make return type of arm64_syscall_trace_enter() bool Jinjie Ruan
2026-09-30 10:18 ` [PATCH v20 13/15] arm64: entry: Convert to generic entry Jinjie Ruan
2026-09-30 10:18 ` [PATCH v20 14/15] arm64: Inline el0_svc_common() Jinjie Ruan
2026-09-30 10:18 ` [PATCH v20 15/15] selftests/arm64: Add ptrace SYSEMU/single-step tests Jinjie Ruan
2026-10-26 8:52 ` [PATCH v20 00/15] arm64: entry: Convert to Generic Entry Jinjie Ruan
2026-11-04 13:38 ` Linus Walleij
2026-11-05 7:49 ` Jinjie Ruan [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=4831fb24-85f2-4273-9cf8-9ac60dd6555f@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=ada.coupriediaz@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kees@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linusw@kernel.org \
--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=peterz@infradead.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=tglx@kernel.org \
--cc=thuth@redhat.com \
--cc=vladimir.murzin@arm.com \
--cc=wad@chromium.org \
--cc=will@kernel.org \
--cc=yeoreum.yun@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
all inboxes | Powered by JetHome®