aboutsummaryrefslogtreecommitdiff
path: root/qga
diff options
context:
space:
mode:
authorDaniel Henrique Barboza <dbarboza@ventanamicro.com>2023-12-08 15:38:31 -0300
committerAlistair Francis <alistair.francis@wdc.com>2024-01-10 18:47:46 +1000
commit49c211ffca00fdf7c0c29072c224e88527a14838 (patch)
tree3528f4d1969dab76ead18592aa5dfb4a999cc809 /qga
parent8d326cb88b03b593708262947e9ec30411fb99ab (diff)
downloadqemu-49c211ffca00fdf7c0c29072c224e88527a14838.zip
qemu-49c211ffca00fdf7c0c29072c224e88527a14838.tar.gz
qemu-49c211ffca00fdf7c0c29072c224e88527a14838.tar.bz2
target/riscv/kvm: change KVM_REG_RISCV_FP_F to u32
KVM_REG_RISCV_FP_F regs have u32 size according to the API, but by using kvm_riscv_reg_id() in RISCV_FP_F_REG() we're returning u64 sizes when running with TARGET_RISCV64. The most likely reason why no one noticed this is because we're not implementing kvm_cpu_synchronize_state() in RISC-V yet. Create a new helper that returns a KVM ID with u32 size and use it in RISCV_FP_F_REG(). Reported-by: Andrew Jones <ajones@ventanamicro.com> Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> Reviewed-by: Andrew Jones <ajones@ventanamicro.com> Message-ID: <20231208183835.2411523-2-dbarboza@ventanamicro.com> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Diffstat (limited to 'qga')
0 files changed, 0 insertions, 0 deletions