From: Will Deacon <will@kernel.org>
To: Ryo Takakura <ryotkkr98@gmail.com>
Cc: catalin.marinas@arm.com, bigeasy@linutronix.de,
clrkwllms@kernel.org, rostedt@goodmis.org, leitao@debian.org,
mark.rutland@arm.com, ardb@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH] arm64: use SOFTIRQ_ON_OWN_STACK for enabling softirq stack
Date: Tue, 4 Nov 2025 13:58:13 +0000 [thread overview]
Message-ID: <aQoGdVYOddu9bxLg@willie-the-truck> (raw)
In-Reply-To: <20251013013508.74677-1-ryotkkr98@gmail.com>
On Mon, Oct 13, 2025 at 01:35:08AM +0000, Ryo Takakura wrote:
> For those architectures with HAVE_SOFTIRQ_ON_OWN_STACK use
> their dedicated softirq stack when !PREEMPT_RT. This condition
> is ensured by SOFTIRQ_ON_OWN_STACK.
>
> Let arm64 use SOFTIRQ_ON_OWN_STACK as well to select its
> usage of the stack.
>
> Signed-off-by: Ryo Takakura <ryotkkr98@gmail.com>
> ---
> arch/arm64/kernel/irq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/irq.c b/arch/arm64/kernel/irq.c
> index c0065a1d77cf..15dedb385b9e 100644
> --- a/arch/arm64/kernel/irq.c
> +++ b/arch/arm64/kernel/irq.c
> @@ -62,7 +62,7 @@ static void __init init_irq_stacks(void)
> }
> }
>
> -#ifndef CONFIG_PREEMPT_RT
> +#ifdef CONFIG_SOFTIRQ_ON_OWN_STACK
> static void ____do_softirq(struct pt_regs *regs)
> {
> __do_softirq();
Acked-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2025-11-04 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 1:35 [PATCH] arm64: use SOFTIRQ_ON_OWN_STACK for enabling softirq stack Ryo Takakura
2025-10-13 6:27 ` Sebastian Andrzej Siewior
2025-11-04 13:58 ` Will Deacon [this message]
2025-11-05 7:33 ` Ryo Takakura
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=aQoGdVYOddu9bxLg@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=clrkwllms@kernel.org \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=rostedt@goodmis.org \
--cc=ryotkkr98@gmail.com \
/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).