From: Heiko Carstens <hca@linux.ibm.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: catalin.marinas@arm.com, will@kernel.org, oleg@redhat.com,
gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com, tglx@kernel.org,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, arnd@arndb.de, shuah@kernel.org, kees@kernel.org,
luto@amacapital.net, wad@chromium.org, kevin.brodsky@arm.com,
charlie@rivosinc.com, macro@orcam.me.uk, deller@gmx.de,
ldv@strace.io, anshuman.khandual@arm.com, song@kernel.org,
ryan.roberts@arm.com, mark.rutland@arm.com,
ada.coupriediaz@arm.com, broonie@kernel.org, pengcan@kylinos.cn,
liqiang01@kylinos.cn, thuth@redhat.com, andreas@gaisler.com,
schuster.simon@siemens-energy.com, jremus@linux.ibm.com,
jgross@suse.com, mathieu.desnoyers@efficios.com,
yeoreum.yun@arm.com, kmal@cock.li, dvyukov@google.com,
akpm@linux-foundation.org, reddybalavignesh9979@gmail.com,
richard.weiyang@gmail.com, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-arch@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v13 11/12] arm64: Use generic TIF bits for common thread flags
Date: Fri, 13 Mar 2026 11:10:22 +0100 [thread overview]
Message-ID: <20260313101022.13729C56-hca@linux.ibm.com> (raw)
In-Reply-To: <20260313094738.3985794-12-ruanjinjie@huawei.com>
On Fri, Mar 13, 2026 at 05:47:37PM +0800, Jinjie Ruan wrote:
> Use the generic TIF bits defined in <asm-generic/thread_info_tif.h> for
> standard thread flags (TIF_SIGPENDING, TIF_NEED_RESCHED, TIF_NOTIFY_RESUME,
> TIF_RESTORE_SIGMASK, TIF_SINGLESTEP, etc.) instead of defining
> them locally.
>
> Arm64-specific bits (TIF_FOREIGN_FPSTATE, TIF_MTE_ASYNC_FAULT, TIF_SVE,
> TIF_SSBD, etc.) are renumbered to start at bit 16 to avoid conflicts.
>
> This enables RSEQ optimizations which require CONFIG_HAVE_GENERIC_TIF_BITS
> combined with the generic entry infrastructure (already used by arm64).
>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
> arch/arm64/Kconfig | 1 +
> arch/arm64/include/asm/thread_info.h | 62 ++++++++++++---------------
> arch/s390/include/asm/thread_info.h | 7 ++-
Acked-by: Heiko Carstens <hca@linux.ibm.com> # s390
> arch/x86/include/asm/thread_info.h | 6 +--
> include/asm-generic/thread_info_tif.h | 5 +++
> 5 files changed, 38 insertions(+), 43 deletions(-)
FWIW, I guess you want to do the same for loongarch was well?
next prev parent reply other threads:[~2026-03-13 10:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 9:47 [PATCH v13 00/12] arm64: entry: Convert to Generic Entry Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 01/12] arm64/ptrace: Refactor syscall_trace_enter/exit() to accept flags parameter Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 02/12] arm64/ptrace: Expand secure_computing() in place Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 03/12] arm64/ptrace: Use syscall_get_arguments() helper for audit Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 04/12] arm64: ptrace: Move rseq_syscall() before audit_syscall_exit() Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 05/12] arm64: syscall: Introduce syscall_exit_to_user_mode_work() Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 06/12] arm64/ptrace: Define and use _TIF_SYSCALL_EXIT_WORK Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 07/12] arm64/ptrace: Skip syscall exit reporting for PTRACE_SYSEMU_SINGLESTEP Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 08/12] arm64: entry: Convert to generic entry Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 09/12] arm64: Inline el0_svc_common() Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 10/12] s390: Rename TIF_SINGLE_STEP to TIF_SINGLESTEP Jinjie Ruan
2026-03-13 10:09 ` Heiko Carstens
2026-03-13 9:47 ` [PATCH v13 11/12] arm64: Use generic TIF bits for common thread flags Jinjie Ruan
2026-03-13 10:10 ` Heiko Carstens [this message]
2026-03-16 8:30 ` Jinjie Ruan
2026-03-13 9:47 ` [PATCH v13 12/12] selftests: sud_test: Support aarch64 Jinjie Ruan
2026-03-13 11:57 ` [PATCH v13 00/12] arm64: entry: Convert to Generic Entry Peter Zijlstra
2026-03-16 9:51 ` 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=20260313101022.13729C56-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=ada.coupriediaz@arm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=charlie@rivosinc.com \
--cc=dave.hansen@linux.intel.com \
--cc=deller@gmx.de \
--cc=dvyukov@google.com \
--cc=gor@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jremus@linux.ibm.com \
--cc=kees@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=kmal@cock.li \
--cc=ldv@strace.io \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=liqiang01@kylinos.cn \
--cc=luto@amacapital.net \
--cc=macro@orcam.me.uk \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.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=schuster.simon@siemens-energy.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=svens@linux.ibm.com \
--cc=tglx@kernel.org \
--cc=thuth@redhat.com \
--cc=wad@chromium.org \
--cc=will@kernel.org \
--cc=x86@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