_2025-03-25_10：58：25_	2025-03-25 10：58：25
[1_5] RISC-V_ KVM_ Forward SEED CSR access to user space - Patchwork
原文链接失效了?试试备份
TAGs:处理器 risc-v ISA zkr
Summary: This text appears to be an email message containing a patch series for the RISC-V KVM (Kernel-based Virtual Machine) project. The patch series is related to forwarding SEED CSR (Control and Status Register) access to user space when the Zkr extension is available to the guest/VM. The patch includes changes to the `arch/riscv/kvm/vcpu_insn.c` file and is signed off by Anup Patel and reviewed by Andrew Jones. The patch series also includes metadata such as the list ID, mailman version, and sender information.此文本似乎是一封电子邮件，其中包含 RISC-V KVM（基于内核的虚拟机）项目的补丁系列。此补丁系列与当 Zkr 扩展可供来宾/VM 使用时将 SEED CSR（控制和状态寄存器）访问转发到用户空间有关。此补丁包括对 'arch/riscv/kvm/vcpu_insn.c' 文件的更改，由 Anup Patel 签署并由 Andrew Jones 审阅。修补程序系列还包括元数据，例如列表 ID、mailman 版本和发件人信息。

_2025-03-25_10：58：17_	2025-03-25 10：58：17
[PULL,02_28] target_riscv_kvm_ Fix exposure of Zkr - Patchwork
原文链接失效了?试试备份
TAGs:处理器 risc-v ISA zkr
Summary: This text is a diff output showing changes made to the RISC-V QEMU emulator code. The changes include adding a new function `riscv_new_csr_seed()` to create a new value for the SEED CSR, and updating the `rmw_seed()` function to use this new function instead of generating a random value directly. The changes also include adding a new case `KVM_EXIT_RISCV_CSR` to the `kvm_arch_handle_exit()` function to handle the CSR EXIT reason.此文本是一个差异输出，显示了对 RISC-V QEMU 仿真器代码所做的更改。这些更改包括添加新函数 'riscv_new_csr_seed（）' 为 SEED CSR 创建新值，以及更新 'rmw_seed（）' 函数以使用此新函数，而不是直接生成随机值。这些更改还包括向 'kvm_arch_handle_exit（）' 函数添加新的 case 'KVM_EXIT_RISCV_CSR' 来处理 CSR EXIT 原因。

_2025-04-10_15：22：41_	2025-04-10 15：22：41
tech-privileged@lists.riscv.org _ [RISC-V] [tech-crypto-ext] Read the seed CSR
原文链接失效了?试试备份
TAGs:处理器 risc-v ISA zkr
Summary: This discussion revolves around the behavior of the seed CSR (Control and Status Register) in a cryptographic system. The seed CSR is designed to ensure that secret entropy words are not made available multiple times for security reasons. When reading the seed CSR, the system clears (wipes) the entropy contents and changes the state to WAIT, unless there is entropy immediately available for ES16. However, there is a discrepancy between the seed CSR specification and the privileged specification regarding the side effects of reads and writes.