From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Mukesh Kumar Chaurasiya <mkchauras@linux.ibm.com>,
chleroy@kernel.org, maddy@linux.ibm.com
Cc: 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,
akpm@linux-foundation.org, macro@orcam.me.uk, deller@gmx.de,
ldv@strace.io, charlie@rivosinc.com, segher@kernel.crashing.org,
bigeasy@linutronix.de, peterz@infradead.org,
namcao@linutronix.de, tglx@linutronix.de,
kan.liang@linux.intel.com, mark.barnett@arm.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/8] powerpc: Enable IRQ generic entry/exit path.
Date: Thu, 1 Jan 2026 23:01:08 +0530 [thread overview]
Message-ID: <25b443c7-cdbc-43c4-8db0-4c5eb3435687@linux.ibm.com> (raw)
In-Reply-To: <20251229045416.3193779-8-mkchauras@linux.ibm.com>
On 12/29/25 10:24 AM, Mukesh Kumar Chaurasiya wrote:
> From: Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>
>
> Enable the generic IRQ entry/exit infrastructure on PowerPC by selecting
> GENERIC_IRQ_ENTRY and integrating the architecture-specific interrupt
> handlers with the generic entry/exit APIs.
>
> This change replaces PowerPC’s local interrupt entry/exit handling with
> calls to the generic irqentry_* helpers, aligning the architecture with
> the common kernel entry model. The macros that define interrupt, async,
> and NMI handlers are updated to use irqentry_enter()/irqentry_exit()
> and irqentry_nmi_enter()/irqentry_nmi_exit() where applicable.
>
> Key updates include:
> - Select GENERIC_IRQ_ENTRY in Kconfig.
> - Replace interrupt_enter/exit_prepare() with arch_interrupt_* helpers.
> - Integrate irqentry_enter()/exit() in standard and async interrupt paths.
> - Integrate irqentry_nmi_enter()/exit() in NMI handlers.
> - Remove redundant irq_enter()/irq_exit() calls now handled generically.
> - Use irqentry_exit_cond_resched() for preemption checks.
> - Remove unused code.
>
> This change establishes the necessary wiring for PowerPC to use the
> generic IRQ entry/exit framework while maintaining existing semantics.
>
> Signed-off-by: Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>
> ---
> arch/powerpc/Kconfig | 1 +
> arch/powerpc/include/asm/entry-common.h | 61 +--
> arch/powerpc/include/asm/interrupt.h | 484 +++---------------------
> arch/powerpc/kernel/interrupt.c | 15 +-
> 4 files changed, 72 insertions(+), 489 deletions(-)
>
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 9537a61ebae0..398cef868c14 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -207,6 +207,7 @@ config PPC
> select GENERIC_GETTIMEOFDAY
> select GENERIC_IDLE_POLL_SETUP
> select GENERIC_IOREMAP
> + select GENERIC_IRQ_ENTRY
> select GENERIC_IRQ_SHOW
> select GENERIC_IRQ_SHOW_LEVEL
> select GENERIC_PCI_IOMAP if PCI
There is no need for GENERIC_IRQ_ENTRY. I don't see a reason why
we need to have both.
Enabling GENERIC_ENTRY which is done in next patch will enable this.
It does the same thing and one less kconfig to worry about.
This would allow some easier code refactoring IMO.
- You can keep adding code to asm/entry-common.h. This will help avoid
moving to interrupt.h in between.
- You can add another patch as cleanup post GENERIC_ENTRY for
easier review for seccomp/ptrace.
...
- Some more ct_warning in arch/powerpc are probably not necessary
(can be done post the series too)
- Some more cleanups can be done w.r.t to lockdep and tracing hardirq etc.
For example in next_interrupt. I think replay soft interrupts will end
up making irqentry_enter/exit calls which does same or similar thing.
(can be done post the series too)
- can we move syscall_exit_prepare/ into kernel/syscall.c?
(can be done post the series too)
next prev parent reply other threads:[~2026-01-01 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 4:54 [PATCH v3 0/8] Generic IRQ entry/exit support for powerpc Mukesh Kumar Chaurasiya
2025-12-29 4:54 ` [PATCH v3 1/8] powerpc: rename arch_irq_disabled_regs Mukesh Kumar Chaurasiya
2025-12-29 4:54 ` [PATCH v3 2/8] powerpc: Prepare to build with generic entry/exit framework Mukesh Kumar Chaurasiya
2025-12-29 4:54 ` [PATCH v3 3/8] powerpc: introduce arch_enter_from_user_mode Mukesh Kumar Chaurasiya
2025-12-29 4:54 ` [PATCH v3 4/8] powerpc: Introduce syscall exit arch functions Mukesh Kumar Chaurasiya
2025-12-29 4:54 ` [PATCH v3 5/8] powerpc: add exit_flags field in pt_regs Mukesh Kumar Chaurasiya
2025-12-29 4:54 ` [PATCH v3 6/8] powerpc: Prepare for IRQ entry exit Mukesh Kumar Chaurasiya
2025-12-29 4:54 ` [PATCH v3 7/8] powerpc: Enable IRQ generic entry/exit path Mukesh Kumar Chaurasiya
2026-01-01 17:31 ` Shrikanth Hegde [this message]
2026-01-06 4:59 ` Mukesh Kumar Chaurasiya
2025-12-29 4:54 ` [PATCH v3 8/8] powerpc: Enable Generic Entry/Exit for syscalls Mukesh Kumar Chaurasiya
2026-01-01 9:07 ` [PATCH v3 0/8] Generic IRQ entry/exit support for powerpc Shrikanth Hegde
2026-01-06 5:01 ` Mukesh Kumar Chaurasiya
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=25b443c7-cdbc-43c4-8db0-4c5eb3435687@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=charlie@rivosinc.com \
--cc=chleroy@kernel.org \
--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=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=tglx@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;
as well as URLs for NNTP newsgroup(s).