From: Qi Zheng <zhengqi.arch@bytedance.com>
To: Will Deacon <will@kernel.org>
Cc: arnd@arndb.de, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] arm64: run softirqs on the per-CPU IRQ stack
Date: Fri, 22 Jul 2022 17:13:39 +0800 [thread overview]
Message-ID: <d540aaff-ec6a-3f25-dd79-b27b4ad81b36@bytedance.com> (raw)
In-Reply-To: <20220722090440.GB18125@willie-the-truck>
On 2022/7/22 17:04, Will Deacon wrote:
> On Fri, Jul 08, 2022 at 05:49:49PM +0800, Qi Zheng wrote:
>> Currently arm64 supports per-CPU IRQ stack, but softirqs
>> are still handled in the task context.
>>
>> Since any call to local_bh_enable() at any level in the task's
>> call stack may trigger a softirq processing run, which could
>> potentially cause a task stack overflow if the combined stack
>> footprints exceed the stack's size, let's run these softirqs
>> on the IRQ stack as well.
>>
>> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
>> ---
>> arch/arm64/Kconfig | 1 +
>> arch/arm64/kernel/irq.c | 13 +++++++++++++
>> 2 files changed, 14 insertions(+)
>>
>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>> index 4c1e1d2d2f8b..be0a9f0052ee 100644
>> --- a/arch/arm64/Kconfig
>> +++ b/arch/arm64/Kconfig
>> @@ -230,6 +230,7 @@ config ARM64
>> select HAVE_ARCH_USERFAULTFD_MINOR if USERFAULTFD
>> select TRACE_IRQFLAGS_SUPPORT
>> select TRACE_IRQFLAGS_NMI_SUPPORT
>> + select HAVE_SOFTIRQ_ON_OWN_STACK
>> help
>> ARM 64-bit (AArch64) Linux support.
>>
>> diff --git a/arch/arm64/kernel/irq.c b/arch/arm64/kernel/irq.c
>> index bda49430c9ea..c36ad20a52f3 100644
>> --- a/arch/arm64/kernel/irq.c
>> +++ b/arch/arm64/kernel/irq.c
>> @@ -22,6 +22,7 @@
>> #include <linux/vmalloc.h>
>> #include <asm/daifflags.h>
>> #include <asm/vmap_stack.h>
>> +#include <asm/exception.h>
>>
>> /* Only access this in an NMI enter/exit */
>> DEFINE_PER_CPU(struct nmi_ctx, nmi_contexts);
>> @@ -71,6 +72,18 @@ static void init_irq_stacks(void)
>> }
>> #endif
>>
>> +#ifndef CONFIG_PREEMPT_RT
>> +static void ____do_softirq(struct pt_regs *regs)
>> +{
>> + __do_softirq();
>> +}
>> +
>> +void do_softirq_own_stack(void)
>> +{
>> + call_on_irq_stack(NULL, ____do_softirq);
>> +}
>> +#endif
>
> Acked-by: Will Deacon <will@kernel.org>
>
> Please can you repost this at -rc1 and we can queue it up for 5.21?
Sure, will do.
Thanks,
Qi
>
> Thanks,
>
> Will
--
Thanks,
Qi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-22 9:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 9:49 [PATCH v1 0/2] arm64: run softirqs on the per-CPU IRQ stack Qi Zheng
2022-07-08 9:49 ` [PATCH v1 1/2] " Qi Zheng
2022-07-14 11:32 ` Arnd Bergmann
2022-07-14 11:50 ` Qi Zheng
2022-07-22 9:04 ` Will Deacon
2022-07-22 9:13 ` Qi Zheng [this message]
2022-07-08 9:49 ` [PATCH v1 2/2] arm64: support HAVE_IRQ_EXIT_ON_IRQ_STACK Qi Zheng
2022-07-14 11:37 ` Arnd Bergmann
2022-07-14 11:54 ` Qi Zheng
2022-07-19 7:01 ` Qi Zheng
2022-07-19 11:24 ` Mark Rutland
2022-07-19 12:11 ` Qi Zheng
2022-07-12 6:57 ` [PATCH v1 0/2] arm64: run softirqs on the per-CPU IRQ stack Qi Zheng
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=d540aaff-ec6a-3f25-dd79-b27b4ad81b36@bytedance.com \
--to=zhengqi.arch@bytedance.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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