On Wed, Feb 25, 2026 at 10:20:25AM +0000, Djordje Todorovic wrote: > Add options to compile riscv64be-softmmu and riscv32be-softmmu > --- > meson.build | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/meson.build b/meson.build > index 8c6c0a9a32..41ad38d184 100644 > --- a/meson.build > +++ b/meson.build > @@ -55,6 +55,11 @@ supported_cpus = ['ppc64', 's390x', 'riscv64', 'x86_64', > > cpu = host_machine.cpu_family() > > +# Unify riscv64be to riscv64. > +if cpu == 'riscv64be' > + cpu = 'riscv64' > +endif > + > target_dirs = config_host['TARGET_DIRS'].split() > > # type of binaries to build > @@ -281,7 +286,7 @@ elif cpu == 'ppc64' > elif cpu == 'mips64' > kvm_targets = ['mips-softmmu', 'mipsel-softmmu', 'mips64-softmmu', > 'mips64el-softmmu'] > elif cpu == 'riscv64' > - kvm_targets = ['riscv64-softmmu'] > + kvm_targets = ['riscv32-softmmu', 'riscv64-softmmu', 'riscv32be-softmmu', > 'riscv64be-softmmu']
The suibject says its adding "BE" targets, but this is also adding a 32-bit little endian target. Does KVM, actually support running riscv32 guests on a riscv64 host ? If so, this change to add 32-bit KVM should likely be done as its own commit separate from this big endian series. With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
