From: patchwork-bot+linux-riscv@kernel.org
To: Andy Chiu <andy.chiu@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, vineetg@rivosinc.com,
greentime.hu@sifive.com, guoren@linux.alibaba.com,
bjorn@rivosinc.com, aou@eecs.berkeley.edu
Subject: Re: [v1, 0/2] Initialize Vector registers in the first-use trap
Date: Tue, 04 Jul 2023 15:02:32 +0000 [thread overview]
Message-ID: <168848295230.29521.2754654664168260934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230627015556.12329-1-andy.chiu@sifive.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 27 Jun 2023 01:55:53 +0000 you wrote:
> Before applying this series, We only initialize the space for saving
> Vector registers. This is not enough as Vector registers themselves also
> neeeded to be initialized before dropping back into userspace. Or, we
> may risk leaking a process's data left in Vector register to another
> process. This can be verified by only applying the second patch and
> running the test.
>
> [...]
Here is the summary with links:
- [v1,1/2] riscv: vector: clear V-reg in the first-use trap
https://git.kernel.org/riscv/c/75b59f2a90aa
- [v1,2/2] selftests: Test RISC-V Vector's first-use handler
https://git.kernel.org/riscv/c/5c93c4c72fbc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-07-04 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 1:55 [v1, 0/2] Initialize Vector registers in the first-use trap Andy Chiu
2023-06-27 1:55 ` [v1, 1/2] riscv: vector: clear V-reg " Andy Chiu
2023-06-27 7:28 ` Björn Töpel
2023-06-27 1:55 ` [v1, 2/2] selftests: Test RISC-V Vector's first-use handler Andy Chiu
2023-06-27 7:46 ` Björn Töpel
2023-06-27 15:39 ` Andy Chiu
2023-07-04 14:42 ` [v1, 0/2] Initialize Vector registers in the first-use trap Palmer Dabbelt
2023-07-04 15:02 ` patchwork-bot+linux-riscv [this message]
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=168848295230.29521.2754654664168260934.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@linux.alibaba.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vineetg@rivosinc.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