From: "Björn Töpel" <bjorn@kernel.org>
To: Guo Ren <guoren@kernel.org>
Cc: arnd@arndb.de, palmer@rivosinc.com, tglx@linutronix.de,
peterz@infradead.org, luto@kernel.org,
conor.dooley@microchip.com, heiko@sntech.de, jszhang@kernel.org,
lazyparser@gmail.com, falcon@tinylab.org, chenhuacai@kernel.org,
apatel@ventanamicro.com, atishp@atishpatra.org,
palmer@dabbelt.com, paul.walmsley@sifive.com,
mark.rutland@arm.com, zouyipeng@huawei.com,
bigeasy@linutronix.de, David.Laight@aculab.com,
chenzhongjin@huawei.com, greentime.hu@sifive.com,
andy.chiu@sifive.com, ben@decadent.org.uk,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH -next V10 09/10] riscv: stack: Support HAVE_SOFTIRQ_ON_OWN_STACK
Date: Fri, 09 Dec 2022 08:49:52 +0100 [thread overview]
Message-ID: <874ju59ftr.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <CAJF2gTT1YNubBG_RMzwsWVXk0X0nwQvTM2r5NjRvVN+1x1RHMw@mail.gmail.com>
Guo Ren <guoren@kernel.org> writes:
> On Thu, Dec 8, 2022 at 6:12 PM Björn Töpel <bjorn@kernel.org> wrote:
>>
>> guoren@kernel.org writes:
>>
>> > From: Guo Ren <guoren@linux.alibaba.com>
>> >
>> > Add the HAVE_SOFTIRQ_ON_OWN_STACK feature for the IRQ_STACKS config. The
>> > irq and softirq use the same independent irq_stack of percpu by time
>> > division multiplexing.
>> >
>> > Tested-by: Jisheng Zhang <jszhang@kernel.org>
>> > Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
>> > Signed-off-by: Guo Ren <guoren@kernel.org>
>> > ---
>> > arch/riscv/Kconfig | 7 ++++---
>> > arch/riscv/kernel/irq.c | 33 +++++++++++++++++++++++++++++++++
>> > 2 files changed, 37 insertions(+), 3 deletions(-)
>> >
>> > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
>> > index 0a9d4bdc0338..bd4c4ae4cdc9 100644
>> > --- a/arch/riscv/Kconfig
>> > +++ b/arch/riscv/Kconfig
>> > @@ -447,12 +447,13 @@ config FPU
>> > If you don't know what to do here, say Y.
>> >
>> > config IRQ_STACKS
>> > - bool "Independent irq stacks" if EXPERT
>> > + bool "Independent irq & softirq stacks" if EXPERT
>> > default y
>> > select HAVE_IRQ_EXIT_ON_IRQ_STACK
>> > + select HAVE_SOFTIRQ_ON_OWN_STACK
>>
>> HAVE_IRQ_EXIT_ON_IRQ_STACK is used by softirq.c Shouldn't that be
>> selected introduced in this patch, instead of the previous one?
> This patch depends on the previous one. And the previous one could
> work separately.
Let me try to be more clear: IRQ_STACKS should be introduced in the
previous patch, which adds per-cpu stacks to hardirq. This patch adds
per-cpu stacks for softirq, and the softirq related selects:
select HAVE_IRQ_EXIT_ON_IRQ_STACK
select HAVE_SOFTIRQ_ON_OWN_STACK
Hence, the "HAVE_IRQ_EXIT_ON_IRQ_STACK" select should be part of *this*
patch, not the previous.
Or am I missing something?
Björn
next prev parent reply other threads:[~2022-12-09 7:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 2:58 [PATCH -next V10 00/10] riscv: Add GENERIC_ENTRY support and related features guoren
2022-12-08 2:58 ` [PATCH -next V10 01/10] compiler_types.h: Add __noinstr_section() for noinstr guoren
2022-12-08 2:58 ` [PATCH -next V10 02/10] riscv: ptrace: Remove duplicate operation guoren
2022-12-08 2:58 ` [PATCH -next V10 03/10] riscv: entry: Add noinstr to prevent instrumentation inserted guoren
2022-12-08 2:58 ` [PATCH -next V10 04/10] riscv: entry: Convert to generic entry guoren
2022-12-08 10:11 ` Björn Töpel
2022-12-10 10:27 ` Guo Ren
2022-12-10 16:05 ` Björn Töpel
2022-12-08 2:58 ` [PATCH -next V10 05/10] riscv: entry: Remove extra level wrappers of trace_hardirqs_{on,off} guoren
2022-12-08 10:11 ` Björn Töpel
2022-12-09 2:01 ` Guo Ren
2022-12-08 2:58 ` [PATCH -next V10 06/10] riscv: entry: Consolidate ret_from_kernel_thread into ret_from_fork guoren
2022-12-08 10:12 ` Björn Töpel
2022-12-09 2:01 ` Guo Ren
2022-12-08 2:58 ` [PATCH -next V10 07/10] riscv: entry: Consolidate general regs saving/restoring guoren
2022-12-08 2:58 ` [PATCH -next V10 08/10] riscv: stack: Support HAVE_IRQ_EXIT_ON_IRQ_STACK guoren
2022-12-08 10:12 ` Björn Töpel
2022-12-09 2:06 ` Guo Ren
2022-12-08 2:58 ` [PATCH -next V10 09/10] riscv: stack: Support HAVE_SOFTIRQ_ON_OWN_STACK guoren
2022-12-08 10:12 ` Björn Töpel
2022-12-09 2:09 ` Guo Ren
2022-12-09 7:49 ` Björn Töpel [this message]
2022-12-10 10:21 ` Guo Ren
2022-12-08 2:58 ` [PATCH -next V10 10/10] riscv: stack: Add config of thread stack size guoren
2022-12-08 10:12 ` Björn Töpel
2022-12-09 2:11 ` Guo Ren
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=874ju59ftr.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=David.Laight@aculab.com \
--cc=andy.chiu@sifive.com \
--cc=apatel@ventanamicro.com \
--cc=arnd@arndb.de \
--cc=atishp@atishpatra.org \
--cc=ben@decadent.org.uk \
--cc=bigeasy@linutronix.de \
--cc=chenhuacai@kernel.org \
--cc=chenzhongjin@huawei.com \
--cc=conor.dooley@microchip.com \
--cc=falcon@tinylab.org \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--cc=lazyparser@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=zouyipeng@huawei.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).