aboutsummaryrefslogtreecommitdiff
path: root/scripts/qapi/parser.py
diff options
context:
space:
mode:
authorDaniel Henrique Barboza <dbarboza@ventanamicro.com>2023-12-18 17:43:20 -0300
committerAlistair Francis <alistair.francis@wdc.com>2024-01-10 18:47:47 +1000
commit0d71f0a34938a6ac11953ae3dbec40113d2838a1 (patch)
tree0fb6fa370e92e3598a75b6e2a4e98842c6517ead /scripts/qapi/parser.py
parent1583ca8aa61e1648d1f340c9a6ae3cd7ba3a82ae (diff)
downloadqemu-0d71f0a34938a6ac11953ae3dbec40113d2838a1.zip
qemu-0d71f0a34938a6ac11953ae3dbec40113d2838a1.tar.gz
qemu-0d71f0a34938a6ac11953ae3dbec40113d2838a1.tar.bz2
target/riscv/kvm: do PR_RISCV_V_SET_CONTROL during realize()
Linux RISC-V vector documentation (Document/arch/riscv/vector.rst) mandates a prctl() in order to allow an userspace thread to use the Vector extension from the host. This is something to be done in realize() time, after init(), when we already decided whether we're using RVV or not. We don't have a realize() callback for KVM yet, so add kvm_cpu_realize() and enable RVV for the thread via PR_RISCV_V_SET_CONTROL. Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> Reviewed-by: Alistair Francis <alistair.francis@wdc.com> Message-ID: <20231218204321.75757-4-dbarboza@ventanamicro.com> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Diffstat (limited to 'scripts/qapi/parser.py')
0 files changed, 0 insertions, 0 deletions