Skip to content

[PW_SID:1122610] [v3] RISC-V: KVM: Zicbo[m|z|p] block sizes should be always present in ONE_REG#2230

Closed
linux-riscv-bot wants to merge 2 commits into
workflow__riscv__fixesfrom
pw1122610
Closed

[PW_SID:1122610] [v3] RISC-V: KVM: Zicbo[m|z|p] block sizes should be always present in ONE_REG#2230
linux-riscv-bot wants to merge 2 commits into
workflow__riscv__fixesfrom
pw1122610

Conversation

@linux-riscv-bot

Copy link
Copy Markdown

PR for series 1122610 applied to workflow__riscv__fixes

Name: [v3] RISC-V: KVM: Zicbo[m|z|p] block sizes should be always present in ONE_REG
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1122610
Version: 3

Linux RISC-V bot and others added 2 commits July 1, 2026 03:48
…_REG

All config and core registers of the KVM RISC-V ONE_REG interface are
expected to be always available to the KVM user-space and the KVM
get-reg-list selftest assumes these registers to be as base registers.

Currently, the Zicbo[m|z|p] block size config registers are only
available when corresponding ISA extension is present on the host
which breaks the above expectation. In fact, KVM get-reg-list selftest
fails when any of the Zicbo[m|z|p] ISA extension is not present on
host. To address this issue, drop the ISA extension checks from
kvm_riscv_vcpu_get/set_reg_config() and copy_config_reg_indices()
functions.

Fixes: 031f9ef ("KVM: riscv: Add KVM_GET_REG_LIST API support")
Fixes: a044ef7 ("RISC-V: KVM: use ENOENT in *_one_reg() when extension is unavailable")
Fixes: 48e2feb ("RISC-V: KVM: Provide UAPI for Zicbop block size")
Fixes: cf05b05 ("RISC-V: KVM: Introduce common kvm_riscv_isa_check_host()")
Signed-off-by: Anup Patel <anup.patel@oss.qualcomm.com>
Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
@linux-riscv-bot
linux-riscv-bot force-pushed the workflow__riscv__fixes branch 7 times, most recently from 869345e to f54dc6c Compare July 13, 2026 20:05
@linux-riscv-bot
linux-riscv-bot deleted the pw1122610 branch July 14, 2026 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants