From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Mukesh Kumar Chaurasiya <mkchauras@linux.ibm.com>,
maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
oleg@redhat.com, kees@kernel.org, luto@amacapital.net,
wad@chromium.org, mchauras@linux.ibm.com, thuth@redhat.com,
sshegde@linux.ibm.com, charlie@rivosinc.com, macro@orcam.me.uk,
akpm@linux-foundation.org, ldv@strace.io, deller@gmx.de,
ankur.a.arora@oracle.com, segher@kernel.crashing.org,
tglx@linutronix.de, thomas.weissschuh@linutronix.de,
peterz@infradead.org, menglong8.dong@gmail.com,
bigeasy@linutronix.de, namcao@linutronix.de,
kan.liang@linux.intel.com, mingo@kernel.org,
atrajeev@linux.vnet.ibm.com, mark.barnett@arm.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 8/8] powerpc: Enable Generic Entry/Exit for syscalls.
Date: Tue, 16 Dec 2025 07:41:11 +0100 [thread overview]
Message-ID: <065e3421-0ae1-4e1b-8384-2157d2c1daf9@kernel.org> (raw)
In-Reply-To: <20251214130245.43664-9-mkchauras@linux.ibm.com>
Le 14/12/2025 à 14:02, Mukesh Kumar Chaurasiya a écrit :
> From: Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>
>
> Convert the PowerPC syscall entry and exit paths to use the generic
> entry/exit framework by selecting GENERIC_ENTRY and integrating with
> the common syscall handling routines.
>
> This change transitions PowerPC away from its custom syscall entry and
> exit code to use the generic helpers such as:
> - syscall_enter_from_user_mode()
> - syscall_exit_to_user_mode()
>
> As part of this migration:
> - The architecture now selects GENERIC_ENTRY in Kconfig.
> - Old tracing, seccomp, and audit handling in ptrace.c is removed in
> favor of generic entry infrastructure.
> - interrupt.c and syscall.c are simplified to delegate context
> management and user exit handling to the generic entry path.
> - The new pt_regs field `exit_flags` introduced earlier is now used
> to carry per-syscall exit state flags (e.g. _TIF_RESTOREALL).
>
> This aligns PowerPC with the common entry code used by other
> architectures and reduces duplicated logic around syscall tracing,
> context tracking, and signal handling.
>
> The performance benchmarks from perf bench basic syscall are below:
>
> perf bench syscall usec/op
>
> | Test | With Patch | Without Patch | % Change |
> | --------------- | ---------- | ------------- | -------- |
> | getppid usec/op | 0.207795 | 0.210373 | -1.22% |
> | getpgid usec/op | 0.206282 | 0.211676 | -2.55% |
> | fork usec/op | 833.986 | 814.809 | +2.35% |
> | execve usec/op | 360.939 | 365.168 | -1.16% |
>
> perf bench syscall ops/sec
>
> | Test | With Patch | Without Patch | % Change |
> | --------------- | ---------- | ------------- | -------- |
> | getppid ops/sec | 48,12,433 | 47,53,459 | +1.24% |
> | getpgid ops/sec | 48,47,744 | 47,24,192 | +2.61% |
> | fork ops/sec | 1,199 | 1,227 | -2.28% |
> | execve ops/sec | 2,770 | 2,738 | +1.16% |
I get about 2% degradation on powerpc 8xx, and it is quite stable over
time when repeating the test.
'perf bench syscall all' on powerpc 8xx (usec per op):
| Test | With Patch | Without Patch | % Change |
| --------------- | ---------- | ------------- | -------- |
| getppid usec/op | 2.63 | 2.63 | ~ 0% |
| getpgid usec/op | 2.26 | 2.22 | +2,80% |
| fork usec/op | 15300 | 15000 | +2,00% |
| execve usec/op | 45700 | 45200 | +1.10% |
Christophe
next prev parent reply other threads:[~2025-12-16 6:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 13:02 [PATCH v2 0/8] Generic IRQ entry/exit support for powerpc Mukesh Kumar Chaurasiya
2025-12-14 13:02 ` [PATCH v2 1/8] powerpc: rename arch_irq_disabled_regs Mukesh Kumar Chaurasiya
2025-12-14 13:02 ` [PATCH v2 2/8] powerpc: Prepare to build with generic entry/exit framework Mukesh Kumar Chaurasiya
2025-12-16 9:27 ` Christophe Leroy (CS GROUP)
2025-12-16 14:42 ` Mukesh Kumar Chaurasiya
2025-12-14 13:02 ` [PATCH v2 3/8] powerpc: introduce arch_enter_from_user_mode Mukesh Kumar Chaurasiya
2025-12-16 9:38 ` Christophe Leroy (CS GROUP)
2025-12-16 14:47 ` Mukesh Kumar Chaurasiya
2025-12-14 13:02 ` [PATCH v2 4/8] powerpc: Introduce syscall exit arch functions Mukesh Kumar Chaurasiya
2025-12-16 9:46 ` Christophe Leroy (CS GROUP)
2025-12-16 14:51 ` Mukesh Kumar Chaurasiya
2025-12-14 13:02 ` [PATCH v2 5/8] powerpc: add exit_flags field in pt_regs Mukesh Kumar Chaurasiya
2025-12-16 9:52 ` Christophe Leroy (CS GROUP)
2025-12-16 14:56 ` Mukesh Kumar Chaurasiya
2025-12-14 13:02 ` [PATCH v2 6/8] powerpc: Prepare for IRQ entry exit Mukesh Kumar Chaurasiya
2025-12-16 9:58 ` Christophe Leroy (CS GROUP)
2025-12-16 15:00 ` Mukesh Kumar Chaurasiya
2025-12-16 22:40 ` Christophe Leroy (CS GROUP)
2025-12-17 4:43 ` Mukesh Kumar Chaurasiya
2025-12-19 4:56 ` Mukesh Kumar Chaurasiya
2025-12-14 13:02 ` [PATCH v2 7/8] powerpc: Enable IRQ generic entry/exit path Mukesh Kumar Chaurasiya
2025-12-16 6:29 ` kernel test robot
2025-12-16 15:02 ` Mukesh Kumar Chaurasiya
2025-12-16 10:43 ` Christophe Leroy (CS GROUP)
2025-12-16 15:06 ` Mukesh Kumar Chaurasiya
2025-12-17 2:10 ` kernel test robot
2025-12-17 21:32 ` kernel test robot
2025-12-14 13:02 ` [PATCH v2 8/8] powerpc: Enable Generic Entry/Exit for syscalls Mukesh Kumar Chaurasiya
2025-12-14 16:20 ` Segher Boessenkool
2025-12-15 18:32 ` Mukesh Kumar Chaurasiya
2025-12-15 20:27 ` kernel test robot
2025-12-16 15:08 ` Mukesh Kumar Chaurasiya
2025-12-16 22:57 ` Christophe Leroy (CS GROUP)
2025-12-16 6:41 ` Christophe Leroy (CS GROUP) [this message]
2025-12-16 15:09 ` Mukesh Kumar Chaurasiya
2025-12-16 11:01 ` Christophe Leroy (CS GROUP)
2025-12-16 15:13 ` Mukesh Kumar Chaurasiya
2026-01-04 12:36 ` [PATCH v2 0/8] Generic IRQ entry/exit support for powerpc Samir M
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=065e3421-0ae1-4e1b-8384-2157d2c1daf9@kernel.org \
--to=chleroy@kernel.org \
--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=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=menglong8.dong@gmail.com \
--cc=mingo@kernel.org \
--cc=mkchauras@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=namcao@linutronix.de \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=segher@kernel.crashing.org \
--cc=sshegde@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--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