From: patchwork-bot+linux-riscv@kernel.org
To: Andy Chiu <tchiu@tenstorrent.com>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
andybnac@gmail.com, dfustini@oss.tenstorrent.com,
greentime.hu@sifive.com, linux-kernel@vger.kernel.org,
olof@lixom.net
Subject: Re: [PATCH v6 0/8] riscv: optimize mode switch latency for Vector
Date: Tue, 06 Oct 2026 09:40:08 +0000 [thread overview]
Message-ID: <179127960878.2107992.9155163918962890142.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260918215154.2481482-1-tchiu@tenstorrent.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:
On Fri, 18 Sep 2026 16:51:14 -0500 you wrote:
> This series provide several optimizations targeting system call latency
> regarding vector context management. Before the series, the kernel
> handled user's vector context in an conservative way, where registers
> were null out and VS is tracked as DIRTY. This introduce excess context
> saving and restoring when there is a context swicth. Also, the kernel
> turned off Vector at the exception entry, making all in-kernel vector
> usecase take the serialization cost, which includes context switch and
> user copies. The cost is not easy to hide as vector code are usually sit
> right after enabling V.
>
> [...]
Here is the summary with links:
- [v6,1/8] riscv: do not read csr in vector context switch
https://git.kernel.org/riscv/c/5fd018c630e2
- [v6,2/8] riscv: vector: refactor context switch for kernel-mode vector
https://git.kernel.org/riscv/c/4740b934ebe7
- [v6,3/8] selftest: riscv: test vectorized user copy
https://git.kernel.org/riscv/c/52318cf0fa6e
- [v6,4/8] riscv: vector: refactor vector context operations
https://git.kernel.org/riscv/c/1a5c75ee3d09
- [v6,5/8] riscv: clarify vector state semantics on syscall and context switch
https://git.kernel.org/riscv/c/cc12e55016ba
- [v6,6/8] riscv: vector: adjust ptrace and signal behavior for INITIAL state
https://git.kernel.org/riscv/c/0d4b43a7734d
- [v6,7/8] selftests: riscv: Extend vector tests for sigreturn and ptrace
https://git.kernel.org/riscv/c/6740ec489dd7
- [v6,8/8] riscv: vector: optimize vstate operations
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-10-06 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 21:51 Andy Chiu
2026-10-06 9:40 ` patchwork-bot+linux-riscv [this message]
2026-10-06 10:01 ` Paul Walmsley
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=179127960878.2107992.9155163918962890142.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=dfustini@oss.tenstorrent.com \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tchiu@tenstorrent.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®