From: Thomas Gleixner <tglx@kernel.org>
To: Jisheng Zhang <jszhang@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Guo Ren <guoren@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-csky@vger.kernel.org
Subject: Re: [PATCH 2/3] genirq: use runtime constant to optimize handle_arch_irq access
Date: Sun, 22 Feb 2026 23:06:11 +0100 [thread overview]
Message-ID: <877bs4wi0c.ffs@tglx> (raw)
In-Reply-To: <20260220090922.1506-3-jszhang@kernel.org>
On Fri, Feb 20 2026 at 17:09, Jisheng Zhang wrote:
> Currently, on GENERIC_IRQ_MULTI_HANDLER platforms, the handle_arch_irq
> is a pointer which is set during booting, and every irq processing needs
> to access it, so it sits in hot code path. We can use the
> runtime constant mechanism which was introduced by Linus to speed up
> its accessing.
The proper solution is to use a static call and update it in
set_handle_irq(). That removes the complete indirect call issue from
the hot path.
Thanks,
tglx
next prev parent reply other threads:[~2026-02-22 22:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 9:09 [PATCH 0/3] use runtime constant to optimize handle_arch_irq access Jisheng Zhang
2026-02-20 9:09 ` [PATCH 1/3] vmlinux.lds.h: add _handle_arch_irq RUNTIME_CONST section Jisheng Zhang
2026-02-24 2:01 ` Guo Ren
2026-02-20 9:09 ` [PATCH 2/3] genirq: use runtime constant to optimize handle_arch_irq access Jisheng Zhang
2026-02-22 22:06 ` Thomas Gleixner [this message]
2026-02-23 12:41 ` Jisheng Zhang
2026-02-23 13:11 ` Mark Rutland
2026-02-23 13:22 ` Jisheng Zhang
2026-02-23 13:55 ` Mark Rutland
2026-02-24 1:40 ` Guo Ren
2026-02-24 1:59 ` Guo Ren
2026-02-20 9:09 ` [PATCH 3/3] arm64: " Jisheng Zhang
2026-02-20 12:34 ` Leo Yan
2026-02-20 13:16 ` Jisheng Zhang
2026-02-20 13:34 ` Jisheng Zhang
2026-02-20 16:47 ` Leo Yan
2026-02-21 0:14 ` Jisheng Zhang
2026-02-23 9:15 ` Leo Yan
2026-02-25 14:40 ` Jisheng Zhang
2026-02-23 12:56 ` Mark Rutland
2026-02-23 12:58 ` Jisheng Zhang
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=877bs4wi0c.ffs@tglx \
--to=tglx@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=will@kernel.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