From: Andy Chiu <tchiu@tenstorrent.com>
To: Paul Walmsley <pjw@kernel.org>
Cc: patchwork-bot+linux-riscv@kernel.org,
linux-riscv@lists.infradead.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: riscv: optimize mode switch latency for Vector
Date: Sat, 17 Oct 2026 01:29:06 -0500 [thread overview]
Message-ID: <atMVshcr7cp5wx6-@Tao-Chiu's-Mac> (raw)
In-Reply-To: <cce463c9-3a77-d21c-56e7-5eaa0a290f14@kernel.org>
On Wed, Oct 07, 2026 at 08:20:18AM -0600, Paul Walmsley wrote:
> On Tue, 6 Oct 2026, patchwork-bot+linux-riscv@kernel.org wrote:
>
> > Hello:
> >
> > This series was applied to riscv/linux.git (for-next)
> > by Paul Walmsley <pjw@kernel.org>:
> >
>
> [ ... ]
>
> > 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)
>
> Just to clarify, I only applied the first three patches, for the reason
> mentioned earlier.
>
Hi Paul, sorry for catching up this late. The whole series should be able
to apply, as the kvm fix is already in the tree. See commit b5060a4aa33d
("RISC-V: KVM: fix vcpu vector context handling for kernel-mode
vector"). Please let me know if you had encountered any issue when
applying my series, I am also happy to respin the rest of the series for
the next release if that works better for you!
Thanks,
Andy
next prev parent reply other threads:[~2026-10-17 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 21:51 [PATCH v6 0/8] " Andy Chiu
2026-10-06 9:40 ` patchwork-bot+linux-riscv
2026-10-07 14:20 ` Paul Walmsley
2026-10-17 6:29 ` Andy Chiu [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='atMVshcr7cp5wx6-@Tao-Chiu'\''s-Mac' \
--to=tchiu@tenstorrent.com \
--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=patchwork-bot+linux-riscv@kernel.org \
--cc=pjw@kernel.org \
/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®