diff options
| author | Daniel Henrique Barboza <dbarboza@ventanamicro.com> | 2023-07-06 07:17:32 -0300 |
|---|---|---|
| committer | Alistair Francis <alistair.francis@wdc.com> | 2023-07-10 22:29:20 +1000 |
| commit | f7a69fa6e6e21580b6e56dac87ad2ab0bf228065 (patch) | |
| tree | e0e0202bc61230d22999bda96d5056075a9d252e /hw/display/vhost-user-gpu.c | |
| parent | 7313fffb40ea9775b38ff2ce73c4d6b0f43edc2f (diff) | |
| download | focaccia-qemu-f7a69fa6e6e21580b6e56dac87ad2ab0bf228065.tar.gz focaccia-qemu-f7a69fa6e6e21580b6e56dac87ad2ab0bf228065.zip | |
target/riscv/kvm.c: add multi-letter extension KVM properties
Let's add KVM user properties for the multi-letter extensions that KVM currently supports: zicbom, zicboz, zihintpause, zbb, ssaia, sstc, svinval and svpbmt. As with MISA extensions, we're using the KVMCPUConfig type to hold information about the state of each extension. However, multi-letter extensions have more cases to cover than MISA extensions, so we're adding an extra 'supported' flag as well. This flag will reflect if a given extension is supported by KVM, i.e. KVM knows how to handle it. This is determined during KVM extension discovery in kvm_riscv_init_multiext_cfg(), where we test for EINVAL errors. Any other error will cause an abort. The use of the 'user_set' is similar to what we already do with MISA extensions: the flag set only if the user is changing the extension state. The 'supported' flag will be used later on to make an exception for users that are disabling multi-letter extensions that are unknown to KVM. Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> Acked-by: Alistair Francis <alistair.francis@wdc.com> Reviewed-by: Andrew Jones <ajones@ventanamicro.com> Message-Id: <20230706101738.460804-15-dbarboza@ventanamicro.com> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Diffstat (limited to 'hw/display/vhost-user-gpu.c')
0 files changed, 0 insertions, 0 deletions