From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: linux-riscv@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Deepak Gupta <debug@rivosinc.com>
Subject: [PATCH 0/3] riscv: minor thread_info.cpu improvements
Date: Tue, 22 Jul 2025 18:05:54 +0200 [thread overview]
Message-ID: <20250722160556.2216925-2-rkrcmar@ventanamicro.com> (raw)
Hello,
I noticed that we give thread_info.cpu two different names in the
assembly, load it as a wider type, and store it suboptimally.
The patches are split for easy review instead of easy backporting:
I could split [2/3] into two patches, and move them before [1/3].
Do we expect someone to actually backport the fixes?
Thanks.
Radim Krčmář (3):
riscv: use TASK_TI_CPU instead of TASK_TI_CPU_NUM
riscv: use lw instead of REG_L when reading int cpu
riscv: pack rv64 thread_info better
arch/riscv/include/asm/asm.h | 2 +-
arch/riscv/include/asm/thread_info.h | 2 +-
arch/riscv/kernel/asm-offsets.c | 1 -
arch/riscv/kernel/entry.S | 2 +-
4 files changed, 3 insertions(+), 4 deletions(-)
--
2.50.0
next reply other threads:[~2025-07-22 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 16:05 Radim Krčmář [this message]
2025-07-22 16:05 ` [PATCH 1/3] riscv: use TASK_TI_CPU instead of TASK_TI_CPU_NUM Radim Krčmář
2025-07-25 14:14 ` Alexandre Ghiti
2025-07-22 16:05 ` [PATCH 2/3] riscv: use lw instead of REG_L when reading int cpu Radim Krčmář
2025-07-25 14:21 ` Alexandre Ghiti
2025-07-22 16:05 ` [PATCH 3/3] riscv: pack rv64 thread_info better Radim Krčmář
2025-07-25 14:30 ` Alexandre Ghiti
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=20250722160556.2216925-2-rkrcmar@ventanamicro.com \
--to=rkrcmar@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=debug@rivosinc.com \
--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: 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®