mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryo Takakura <ryotkkr98@gmail.com>
To: will@kernel.org, bigeasy@linutronix.de
Cc: ardb@kernel.org, catalin.marinas@arm.com, clrkwllms@kernel.org,
	leitao@debian.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
	mark.rutland@arm.com, rostedt@goodmis.org, ryotkkr98@gmail.com
Subject: Re: [PATCH] arm64: use SOFTIRQ_ON_OWN_STACK for enabling softirq stack
Date: Wed,  5 Nov 2025 16:33:20 +0900	[thread overview]
Message-ID: <20251105073320.208335-1-ryotkkr98@gmail.com> (raw)
In-Reply-To: <aQoGdVYOddu9bxLg@willie-the-truck>

Hi!

On Tue, 4 Nov 2025 13:58:13 +0000, Will Deacon wrote:
>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>

Thanks Sebastian and Will for checking!
I'll shortly send v2 with the tags.

Sincerely,
Ryo Takakura

>Will

      reply	other threads:[~2025-11-05  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13  1:35 Ryo Takakura
2025-10-13  6:27 ` Sebastian Andrzej Siewior
2025-11-04 13:58 ` Will Deacon
2025-11-05  7:33   ` Ryo Takakura [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=20251105073320.208335-1-ryotkkr98@gmail.com \
    --to=ryotkkr98@gmail.com \
    --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=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

all inboxes | Powered by JetHome®