From: Catalin Marinas <catalin.marinas@arm•com>
To: Breno Leitao <leitao@debian•org>
Cc: Will Deacon <will@kernel•org>,
mark.rutland@arm•com, leo.bras@arm•com, leo.yan@arm•com,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, palmer@dabbelt•com,
paulmck@kernel•org, puranjay@kernel•org, usama.arif@linux•dev,
rmikey@meta•com, kernel-team@meta•com
Subject: Re: [PATCH v2] arm64/irqflags: __always_inline the arch_local_irq_*() helpers
Date: Mon, 27 Apr 2026 13:26:18 +0100 [thread overview]
Message-ID: <ae9V6jrYEwa6Uwqn@arm.com> (raw)
In-Reply-To: <20260421-arm64_always_inline-v2-1-c59d1400514d@debian.org>
On Tue, Apr 21, 2026 at 08:58:57AM -0700, Breno Leitao wrote:
> Force-inline all of the arch_local_irq_*() wrappers so they cannot be
> emitted out-of-line:
>
> - arch_local_irq_enable()
> - arch_local_irq_disable()
> - arch_local_save_flags()
> - arch_irqs_disabled_flags()
> - arch_irqs_disabled()
> - arch_local_irq_save()
> - arch_local_irq_restore()
I'll queue this, thanks!
I think we should also do local_daif_{mask,restore,inherit} as they seem
to be called from noinstr locations in entry-common.c.
--
Catalin
next prev parent reply other threads:[~2026-04-27 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 15:58 [PATCH v2] arm64/irqflags: __always_inline the arch_local_irq_*() helpers Breno Leitao
2026-04-21 16:07 ` Leonardo Bras
2026-04-23 16:45 ` Breno Leitao
2026-04-27 12:26 ` Catalin Marinas [this message]
2026-04-27 13:08 ` Mark Rutland
2026-04-27 14:01 ` [PATCH] arm64/daifflags: Make local_daif_*() helpers __always_inline Leonardo Bras
2026-05-19 10:39 ` Will Deacon
2026-05-19 11:38 ` Leonardo Bras
2026-04-27 13:44 ` [PATCH v2] arm64/irqflags: __always_inline the arch_local_irq_*() helpers Catalin Marinas
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=ae9V6jrYEwa6Uwqn@arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=kernel-team@meta$(echo .)com \
--cc=leitao@debian$(echo .)org \
--cc=leo.bras@arm$(echo .)com \
--cc=leo.yan@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=palmer@dabbelt$(echo .)com \
--cc=paulmck@kernel$(echo .)org \
--cc=puranjay@kernel$(echo .)org \
--cc=rmikey@meta$(echo .)com \
--cc=usama.arif@linux$(echo .)dev \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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