diff options
author | Daniel Henrique Barboza <dbarboza@ventanamicro.com> | 2023-07-06 07:17:26 -0300 |
---|---|---|
committer | Alistair Francis <alistair.francis@wdc.com> | 2023-07-10 22:29:15 +1000 |
commit | 1fb5a622f7ef0cfd65b39decd768983e1d0ba1c2 (patch) | |
tree | 829d55f65654e75256d939b050f5f9f5bf37cfe5 /qapi/string-output-visitor.c | |
parent | d758f8849851dd4e97a575e52c11ec748ab1bbec (diff) | |
download | qemu-1fb5a622f7ef0cfd65b39decd768983e1d0ba1c2.zip qemu-1fb5a622f7ef0cfd65b39decd768983e1d0ba1c2.tar.gz qemu-1fb5a622f7ef0cfd65b39decd768983e1d0ba1c2.tar.bz2 |
target/riscv: handle mvendorid/marchid/mimpid for KVM CPUs
After changing user validation for mvendorid/marchid/mimpid to guarantee
that the value is validated on user input time, coupled with the work in
fetching KVM default values for them by using a scratch CPU, we're
certain that the values in cpu->cfg.(mvendorid|marchid|mimpid) are
already good to be written back to KVM.
There's no need to write the values back for 'host' type CPUs since the
values can't be changed, so let's do that just for generic CPUs.
Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
Acked-by: Alistair Francis <alistair.francis@wdc.com>
Message-Id: <20230706101738.460804-9-dbarboza@ventanamicro.com>
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Diffstat (limited to 'qapi/string-output-visitor.c')
0 files changed, 0 insertions, 0 deletions