From: Thomas Gleixner <tglx@linutronix.de>
To: Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>,
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, mchauras@linux.ibm.com,
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,
sshegde@linux.ibm.com, naveen@kernel.org,
thomas.weissschuh@linutronix.de, Jason@zx2c4.com,
peterz@infradead.org, 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 0/8] Generic IRQ entry/exit support for powerpc
Date: Wed, 10 Sep 2025 22:34:13 +0200 [thread overview]
Message-ID: <87ikhqrqre.ffs@tglx> (raw)
In-Reply-To: <20250908210235.137300-2-mchauras@linux.ibm.com>
On Tue, Sep 09 2025 at 02:32, 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 on ppc64le.
>
> The performance benchmarks from perf bench basic syscall are below:
>
> | Metric | W/O Generic Framework | With Generic Framework | Improvement |
> | ---------- | --------------------- | ---------------------- | ----------- |
> | Total time | 0.885 [sec] | 0.880 [sec] | ~0.56% |
> | usecs/op | 0.088518 | 0.088005 | ~0.58% |
> | ops/sec | 1,12,97,086 | 1,13,62,977 | ~0.58% |
>
> Thats close to 0.6% improvement with this.
Cool!
> 18 files changed, 698 insertions(+), 810 deletions(-)
Thanks for moving ppc over to this. Makes everyones life easier!
tglx
prev parent reply other threads:[~2025-09-10 20:34 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
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 ` Thomas Gleixner [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=87ikhqrqre.ffs@tglx \
--to=tglx@linutronix.de \
--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=sshegde@linux.ibm.com \
--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