Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3] arm64: run softirqs on the per-CPU IRQ stack
Date: Wed, 7 Sep 2022 14:34:27 +0100	[thread overview]
Message-ID: <20220907133426.GA30248@willie-the-truck> (raw)
In-Reply-To: <430e3e5f-d446-6307-cba0-6f859bce560f@bytedance.com>

On Wed, Sep 07, 2022 at 03:04:48PM +0800, Qi Zheng wrote:
> 
> 
> On 2022/8/26 12:16, Qi Zheng wrote:
> > 
> > 
> > On 2022/8/15 20:47, 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>
> > > Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> > > Acked-by: Will Deacon <will@kernel.org>
> > > ---
> > > v2: https://lore.kernel.org/lkml/20220802065325.39740-1-zhengqi.arch@bytedance.com/
> > > v1: https://lore.kernel.org/lkml/20220708094950.41944-1-zhengqi.arch@bytedance.com/
> > > RFC: https://lore.kernel.org/lkml/20220707110511.52129-1-zhengqi.arch@bytedance.com/
> > > 
> > > Changelog in v2 -> v3:
> > >   - rebase onto the v6.0-rc1
> 
> Hi Will,
> 
> Are we good to merge this patch? Or if there is anything else I need to
> do, please let me know. :)

I'm expecting Catalin to pick this one up for 6.1.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-07 13:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 12:47 [PATCH v3] arm64: run softirqs on the per-CPU IRQ stack Qi Zheng
2022-08-26  4:16 ` Qi Zheng
2022-09-07  7:04   ` Qi Zheng
2022-09-07 13:34     ` Will Deacon [this message]
2022-09-07 14:50       ` Qi Zheng
2022-09-08 18:34 ` 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=20220907133426.GA30248@willie-the-truck \
    --to=will@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=zhengqi.arch@bytedance.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