[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <168860030759.22647.12460788590492187878.b4-ty@rivosinc.com>
Date: Wed, 05 Jul 2023 16:38:27 -0700
From: Palmer Dabbelt <palmer@...osinc.com>
To: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
linux-riscv@...ts.infradead.org, Andy Chiu <andy.chiu@...ive.com>,
=C3=B6rn_T=C3=B6pel?= <bjorn@...nel.org>
Cc: =C3=B6rn_T=C3=B6pel?= <bjorn@...osinc.com>,
linux-kernel@...r.kernel.org, linux@...osinc.com,
C3=A9mi_Denis-Courmont?= <remi@...lab.net>,
Darius Rad <darius@...espec.com>,
Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v4] riscv: Discard vector state on syscalls
On Thu, 29 Jun 2023 16:22:28 +0200, Björn Töpel wrote:
> The RISC-V vector specification states:
> Executing a system call causes all caller-saved vector registers
> (v0-v31, vl, vtype) and vstart to become unspecified.
>
> The vector registers are set to all 1s, vill is set (invalid), and the
> vector status is set to Dirty.
>
> [...]
Applied, thanks!
[1/1] riscv: Discard vector state on syscalls
https://git.kernel.org/palmer/c/9657e9b7d253
Best regards,
--
Palmer Dabbelt <palmer@...osinc.com>
Powered by blists - more mailing lists