From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Mukesh Kumar Chaurasiya <mkchauras@linux.ibm.com>,
maddy@linux.ibm.com, chleroy@kernel.org,
linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com, ryabinin.a.a@gmail.com, glider@google.com,
andreyknvl@gmail.com, dvyukov@google.com,
vincenzo.frascino@arm.com, oleg@redhat.com, kees@kernel.org,
luto@amacapital.net, wad@chromium.org, mchauras@linux.ibm.com,
thuth@redhat.com, ruanjinjie@huawei.com,
akpm@linux-foundation.org, charlie@rivosinc.com, deller@gmx.de,
ldv@strace.io, macro@orcam.me.uk, segher@kernel.crashing.org,
peterz@infradead.org, bigeasy@linutronix.de,
namcao@linutronix.de, tglx@linutronix.de, mark.barnett@arm.com,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
mpe@ellerman.id.au
Subject: Re: [PATCH v4 0/8] Generic IRQ entry/exit support for powerpc
Date: Fri, 23 Jan 2026 23:24:15 +0530 [thread overview]
Message-ID: <fe290d99-e81b-4af1-ac2f-5b2a603f2311@linux.ibm.com> (raw)
In-Reply-To: <20260123073916.956498-1-mkchauras@linux.ibm.com>
Hi Mukesh.
On 1/23/26 1:09 PM, Mukesh Kumar Chaurasiya wrote:
> Adding support for the generic irq entry/exit handling for PowerPC. The
> goal is to bring PowerPC in line with other architectures that already
> use the common irq entry infrastructure, reducing duplicated code and
> making it easier to share future changes in entry/exit paths.
>
> This is slightly tested of ppc64le and ppc32.
>
> The performance benchmarks are below:
>
> perf bench syscall usec/op (-ve is improvement)
>
> | Syscall | Base | test | change % |
> | ------- | ----------- | ----------- | -------- |
> | basic | 0.093543 | 0.093023 | -0.56 |
> | execve | 446.557781 | 450.107172 | +0.79 |
> | fork | 1142.204391 | 1156.377214 | +1.24 |
> | getpgid | 0.097666 | 0.092677 | -5.11 |
>
> perf bench syscall ops/sec (+ve is improvement)
>
> | Syscall | Base | New | change % |
> | ------- | -------- | -------- | -------- |
> | basic | 10690548 | 10750140 | +0.56 |
> | execve | 2239 | 2221 | -0.80 |
> | fork | 875 | 864 | -1.26 |
> | getpgid | 10239026 | 10790324 | +5.38 |
>
>
> IPI latency benchmark (-ve is improvement)
>
> | Metric | Base (ns) | New (ns) | % Change |
> | -------------- | ------------- | ------------- | -------- |
> | Dry run | 583136.56 | 584136.35 | 0.17% |
> | Self IPI | 4167393.42 | 4149093.90 | -0.44% |
> | Normal IPI | 61769347.82 | 61753728.39 | -0.03% |
> | Broadcast IPI | 2235584825.02 | 2227521401.45 | -0.36% |
> | Broadcast lock | 2164964433.31 | 2125658641.76 | -1.82% |
>
>
> Thats very close to performance earlier with arch specific handling.
>
> Tests done:
> - Build and boot on ppc64le pseries.
> - Build and boot on ppc64le powernv8 powernv9 powernv10.
> - Build and boot on ppc32.
> - Performance benchmark done with perf syscall basic on pseries.
>
> Changelog:
> V3 -> V4
> - Fixed the issue in older gcc version where linker couldn't find
> mem functions
> - Merged IRQ enable and syscall enable into a single patch
> - Cleanup for unused functions done in separate patch.
> - Some other cosmetic changes
> V3: https://lore.kernel.org/all/20251229045416.3193779-1-mkchauras@linux.ibm.com/
>
> V2 -> V3
> - #ifdef CONFIG_GENERIC_IRQ_ENTRY removed from unnecessary places
> - Some functions made __always_inline
> - pt_regs padding changed to match 16byte interrupt stack alignment
> - And some cosmetic changes from reviews from earlier patch
> V2: https://lore.kernel.org/all/20251214130245.43664-1-mkchauras@linux.ibm.com/
>
> V1 -> V2
> - Fix an issue where context tracking was showing warnings for
> incorrect context
> V1: https://lore.kernel.org/all/20251102115358.1744304-1-mkchauras@linux.ibm.com/
>
> RFC -> PATCH V1
> - Fix for ppc32 spitting out kuap lock warnings.
> - ppc64le powernv8 crash fix.
> - Review comments incorporated from previous RFC.
> RFC https://lore.kernel.org/all/20250908210235.137300-2-mchauras@linux.ibm.com/
>
> Mukesh Kumar Chaurasiya (8):
> powerpc: rename arch_irq_disabled_regs
> powerpc: Prepare to build with generic entry/exit framework
> powerpc: introduce arch_enter_from_user_mode
> powerpc: Introduce syscall exit arch functions
> powerpc: add exit_flags field in pt_regs
> powerpc: Prepare for IRQ entry exit
> powerpc: Enable GENERIC_ENTRY feature
> powerpc: Remove unused functions
>
> arch/powerpc/Kconfig | 1 +
> arch/powerpc/include/asm/entry-common.h | 533 ++++++++++++++++++++++++
> arch/powerpc/include/asm/hw_irq.h | 4 +-
> arch/powerpc/include/asm/interrupt.h | 386 +++--------------
> arch/powerpc/include/asm/kasan.h | 15 +-
> arch/powerpc/include/asm/ptrace.h | 6 +-
> arch/powerpc/include/asm/signal.h | 1 -
> arch/powerpc/include/asm/stacktrace.h | 6 +
> arch/powerpc/include/asm/syscall.h | 5 +
> arch/powerpc/include/asm/thread_info.h | 1 +
> arch/powerpc/include/uapi/asm/ptrace.h | 14 +-
> arch/powerpc/kernel/interrupt.c | 254 ++---------
> arch/powerpc/kernel/ptrace/ptrace.c | 142 +------
> arch/powerpc/kernel/signal.c | 25 +-
> arch/powerpc/kernel/syscall.c | 119 +-----
> arch/powerpc/kernel/traps.c | 2 +-
> arch/powerpc/kernel/watchdog.c | 2 +-
> arch/powerpc/perf/core-book3s.c | 2 +-
> 18 files changed, 690 insertions(+), 828 deletions(-)
> create mode 100644 arch/powerpc/include/asm/entry-common.h
>
Ran it a bit on powernv (power9) too. Not warnings and similar
micro benchmark numbers.
I think this is in better shape now. With that,
for the series.
Reviewed-by: Shrikanth Hegde <sshegde@linux.ibm.com>
next prev parent reply other threads:[~2026-01-23 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 7:39 [PATCH v4 0/8] Generic IRQ entry/exit support for powerpc Mukesh Kumar Chaurasiya
2026-01-23 7:39 ` [PATCH v4 1/8] powerpc: rename arch_irq_disabled_regs Mukesh Kumar Chaurasiya
2026-01-23 7:39 ` [PATCH v4 2/8] powerpc: Prepare to build with generic entry/exit framework Mukesh Kumar Chaurasiya
2026-01-23 7:39 ` [PATCH v4 3/8] powerpc: introduce arch_enter_from_user_mode Mukesh Kumar Chaurasiya
2026-01-23 7:39 ` [PATCH v4 4/8] powerpc: Introduce syscall exit arch functions Mukesh Kumar Chaurasiya
2026-01-23 7:39 ` [PATCH v4 5/8] powerpc: add exit_flags field in pt_regs Mukesh Kumar Chaurasiya
2026-01-23 7:39 ` [PATCH v4 6/8] powerpc: Prepare for IRQ entry exit Mukesh Kumar Chaurasiya
2026-01-23 7:39 ` [PATCH v4 7/8] powerpc: Enable GENERIC_ENTRY feature Mukesh Kumar Chaurasiya
2026-01-23 7:39 ` [PATCH v4 8/8] powerpc: Remove unused functions Mukesh Kumar Chaurasiya
2026-01-23 17:54 ` Shrikanth Hegde [this message]
2026-01-30 7:24 ` [PATCH v4 0/8] Generic IRQ entry/exit support for powerpc Venkat
2026-01-30 8:41 ` David Gow
2026-01-30 18:14 ` 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=fe290d99-e81b-4af1-ac2f-5b2a603f2311@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=charlie@rivosinc.com \
--cc=chleroy@kernel.org \
--cc=deller@gmx.de \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.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=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=ruanjinjie@huawei.com \
--cc=ryabinin.a.a@gmail.com \
--cc=segher@kernel.crashing.org \
--cc=tglx@linutronix.de \
--cc=thuth@redhat.com \
--cc=vincenzo.frascino@arm.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