From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>
Cc: maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, oleg@redhat.com, kees@kernel.org,
luto@amacapital.net, wad@chromium.org, deller@gmx.de,
ldv@strace.io, macro@orcam.me.uk, charlie@rivosinc.com,
akpm@linux-foundation.org, bigeasy@linutronix.de,
ankur.a.arora@oracle.com, naveen@kernel.org,
thomas.weissschuh@linutronix.de, Jason@zx2c4.com,
peterz@infradead.org, tglx@linutronix.de, namcao@linutronix.de,
kan.liang@linux.intel.com, mingo@kernel.org,
oliver.upton@linux.dev, mark.barnett@arm.com,
atrajeev@linux.vnet.ibm.com, rppt@kernel.org,
coltonlewis@google.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC V2 2/8] powerpc: Prepare to build with generic entry/exit framework
Date: Sat, 13 Sep 2025 18:19:05 +0530 [thread overview]
Message-ID: <b347f6e2-26c0-486f-85c7-b2877b9f1189@linux.ibm.com> (raw)
In-Reply-To: <20250908210235.137300-4-mchauras@linux.ibm.com>
On 9/9/25 2:32 AM, Mukesh Kumar Chaurasiya wrote:
> Enabling build with generic entry/exit framework for powerpc
> architecture requires few necessary steps.
>
> Introducing minor infrastructure updates to prepare for future generic
> framework handling:
>
> - Add syscall_work field to struct thread_info for SYSCALL_WORK_* flags.
> - Provide arch_syscall_is_vdso_sigreturn() stub, returning false.
> - Add on_thread_stack() helper to test whether the current stack pointer
> lies within the task’s kernel stack.
>
> No functional change is intended with this patch.
>
> Signed-off-by: Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>
> ---
> arch/powerpc/include/asm/entry-common.h | 11 +++++++++++
> arch/powerpc/include/asm/stacktrace.h | 8 ++++++++
> arch/powerpc/include/asm/syscall.h | 5 +++++
> arch/powerpc/include/asm/thread_info.h | 1 +
> 4 files changed, 25 insertions(+)
> create mode 100644 arch/powerpc/include/asm/entry-common.h
>
> diff --git a/arch/powerpc/include/asm/entry-common.h b/arch/powerpc/include/asm/entry-common.h
> new file mode 100644
> index 0000000000000..3af16d821d07e
> --- /dev/null
> +++ b/arch/powerpc/include/asm/entry-common.h
> @@ -0,0 +1,11 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +
> +#ifndef _ASM_PPC_ENTRY_COMMON_H
> +#define _ASM_PPC_ENTRY_COMMON_H
> +
> +#ifdef CONFIG_GENERIC_IRQ_ENTRY
> +
> +#include <asm/stacktrace.h>
> +
> +#endif /* CONFIG_GENERIC_IRQ_ENTRY */
> +#endif /* _ASM_PPC_ENTRY_COMMON_H */
> diff --git a/arch/powerpc/include/asm/stacktrace.h b/arch/powerpc/include/asm/stacktrace.h
> index 6149b53b3bc8e..3f0a242468813 100644
> --- a/arch/powerpc/include/asm/stacktrace.h
> +++ b/arch/powerpc/include/asm/stacktrace.h
> @@ -8,6 +8,14 @@
> #ifndef _ASM_POWERPC_STACKTRACE_H
> #define _ASM_POWERPC_STACKTRACE_H
>
> +#include <linux/sched.h>
nit:
Is sched.h needed? I don't see any reference here.
It compiled for me without it.
> +
> void show_user_instructions(struct pt_regs *regs);
>
> +static inline bool on_thread_stack(void)
> +{
> + return !(((unsigned long)(current->stack) ^ current_stack_pointer)
> + & ~(THREAD_SIZE -1));
> +}
> +
> #endif /* _ASM_POWERPC_STACKTRACE_H */
> diff --git a/arch/powerpc/include/asm/syscall.h b/arch/powerpc/include/asm/syscall.h
> index 4b3c52ed6e9d2..834fcc4f7b543 100644
> --- a/arch/powerpc/include/asm/syscall.h
> +++ b/arch/powerpc/include/asm/syscall.h
> @@ -139,4 +139,9 @@ static inline int syscall_get_arch(struct task_struct *task)
> else
> return AUDIT_ARCH_PPC64;
> }
> +
> +static inline bool arch_syscall_is_vdso_sigreturn(struct pt_regs *regs)
> +{
> + return false;
> +}
> #endif /* _ASM_SYSCALL_H */
> diff --git a/arch/powerpc/include/asm/thread_info.h b/arch/powerpc/include/asm/thread_info.h
> index 2785c7462ebf7..d0e87c9bae0b0 100644
> --- a/arch/powerpc/include/asm/thread_info.h
> +++ b/arch/powerpc/include/asm/thread_info.h
> @@ -54,6 +54,7 @@
> struct thread_info {
> int preempt_count; /* 0 => preemptable,
> <0 => BUG */
> + unsigned long syscall_work; /* SYSCALL_WORK_ flags */
Can this go after cpu ? it would be 8 byte aligned then. Since it is in
fast path, might help.
> #ifdef CONFIG_SMP
> unsigned int cpu;
> #endif
next prev parent reply other threads:[~2025-09-13 12:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 21:02 [RFC V2 0/8] Generic IRQ entry/exit support for powerpc Mukesh Kumar Chaurasiya
2025-09-08 21:02 ` [RFC V2 1/8] powerpc: rename arch_irq_disabled_regs Mukesh Kumar Chaurasiya
2025-09-13 12:50 ` Shrikanth Hegde
2025-09-08 21:02 ` [RFC V2 2/8] powerpc: Prepare to build with generic entry/exit framework Mukesh Kumar Chaurasiya
2025-09-13 12:49 ` Shrikanth Hegde [this message]
2025-09-16 4:16 ` Mukesh Kumar Chaurasiya
2025-09-08 21:02 ` [RFC V2 3/8] powerpc: introduce arch_enter_from_user_mode Mukesh Kumar Chaurasiya
2025-09-14 9:02 ` Shrikanth Hegde
2025-09-16 4:19 ` Mukesh Kumar Chaurasiya
2025-09-08 21:02 ` [RFC V2 4/8] powerpc: Introduce syscall exit arch functions Mukesh Kumar Chaurasiya
2025-09-08 21:02 ` [RFC V2 5/8] powerpc: add exit_flags field in pt_regs Mukesh Kumar Chaurasiya
2025-09-08 21:02 ` [RFC V2 6/8] powerpc: Prepare for IRQ entry exit Mukesh Kumar Chaurasiya
2025-09-08 21:02 ` [RFC V2 7/8] powerpc: Enable IRQ generic entry/exit path Mukesh Kumar Chaurasiya
2025-09-16 4:16 ` Shrikanth Hegde
2025-09-18 6:55 ` Mukesh Kumar Chaurasiya
2025-09-08 21:02 ` [RFC V2 8/8] powerpc: Enable Generic Entry/Exit for syscalls Mukesh Kumar Chaurasiya
2025-09-09 6:54 ` Shrikanth Hegde
2025-09-09 8:46 ` Mukesh Kumar Chaurasiya
2025-09-18 6:57 ` Mukesh Kumar Chaurasiya
2025-09-10 20:34 ` [RFC V2 0/8] Generic IRQ entry/exit support for powerpc Thomas Gleixner
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=b347f6e2-26c0-486f-85c7-b2877b9f1189@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=ankur.a.arora@oracle.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=charlie@rivosinc.com \
--cc=christophe.leroy@csgroup.eu \
--cc=coltonlewis@google.com \
--cc=deller@gmx.de \
--cc=kan.liang@linux.intel.com \
--cc=kees@kernel.org \
--cc=ldv@strace.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@amacapital.net \
--cc=macro@orcam.me.uk \
--cc=maddy@linux.ibm.com \
--cc=mark.barnett@arm.com \
--cc=mchauras@linux.ibm.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=namcao@linutronix.de \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=oliver.upton@linux.dev \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--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
all inboxes | Powered by JetHome®