From: Jisheng Zhang <jszhang@kernel.org> To: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu> Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [RFC PATCH] riscv: reduce THREAD_SIZE from 16KB to 8KB for RV64 Date: Mon, 7 Feb 2022 01:43:59 +0800 [thread overview] Message-ID: <20220206174359.2986-1-jszhang@kernel.org> (raw) After irq stack is supported, it's possible to use small THREAD_SIZE. In fact, I tested this patch on a Lichee RV board, looks good so far. Signed-off-by: Jisheng Zhang <jszhang@kernel.org> --- arch/riscv/include/asm/thread_info.h | 4 ---- 1 file changed, 4 deletions(-) diff --git a/arch/riscv/include/asm/thread_info.h b/arch/riscv/include/asm/thread_info.h index 67387a8bcb34..fdbf3890a1ab 100644 --- a/arch/riscv/include/asm/thread_info.h +++ b/arch/riscv/include/asm/thread_info.h @@ -12,11 +12,7 @@ #include <linux/const.h> /* thread information allocation */ -#ifdef CONFIG_64BIT -#define THREAD_SIZE_ORDER (2) -#else #define THREAD_SIZE_ORDER (1) -#endif #define THREAD_SIZE (PAGE_SIZE << THREAD_SIZE_ORDER) #define IRQ_STACK_SIZE THREAD_SIZE -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@kernel.org> To: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu> Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [RFC PATCH] riscv: reduce THREAD_SIZE from 16KB to 8KB for RV64 Date: Mon, 7 Feb 2022 01:43:59 +0800 [thread overview] Message-ID: <20220206174359.2986-1-jszhang@kernel.org> (raw) After irq stack is supported, it's possible to use small THREAD_SIZE. In fact, I tested this patch on a Lichee RV board, looks good so far. Signed-off-by: Jisheng Zhang <jszhang@kernel.org> --- arch/riscv/include/asm/thread_info.h | 4 ---- 1 file changed, 4 deletions(-) diff --git a/arch/riscv/include/asm/thread_info.h b/arch/riscv/include/asm/thread_info.h index 67387a8bcb34..fdbf3890a1ab 100644 --- a/arch/riscv/include/asm/thread_info.h +++ b/arch/riscv/include/asm/thread_info.h @@ -12,11 +12,7 @@ #include <linux/const.h> /* thread information allocation */ -#ifdef CONFIG_64BIT -#define THREAD_SIZE_ORDER (2) -#else #define THREAD_SIZE_ORDER (1) -#endif #define THREAD_SIZE (PAGE_SIZE << THREAD_SIZE_ORDER) #define IRQ_STACK_SIZE THREAD_SIZE -- 2.34.1 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-02-06 17:51 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-06 17:43 Jisheng Zhang [this message] 2022-02-06 17:43 ` [RFC PATCH] riscv: reduce THREAD_SIZE from 16KB to 8KB for RV64 Jisheng Zhang 2022-02-07 3:35 ` David Laight 2022-02-07 3:35 ` David Laight 2022-02-07 7:35 ` Arnd Bergmann 2022-02-07 7:35 ` Arnd Bergmann 2022-02-07 15:27 ` Jisheng Zhang 2022-02-07 15:27 ` Jisheng Zhang 2022-02-07 8:05 ` David Abdurachmanov 2022-02-07 8:05 ` David Abdurachmanov 2022-02-07 8:38 ` Andreas Schwab 2022-02-07 8:38 ` Andreas Schwab 2022-02-07 9:07 ` Arnd Bergmann 2022-02-07 9:07 ` Arnd Bergmann
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=20220206174359.2986-1-jszhang@kernel.org \ --to=jszhang@kernel.org \ --cc=aou@eecs.berkeley.edu \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.