On Thu, Sep 25, 2025 at 20:07:19 +0200, Andrea Bolognani via Devel wrote: > Similar to loongarch64, the current behavior is a result > of the way the existing code was written rather than a > consequence of an intentional choice. Make the two > architectures behave the same way, as they should have > from the start. > > Signed-off-by: Andrea Bolognani <abolo...@redhat.com> > --- > src/qemu/qemu_domain.c | 3 +- > ...ault-models.riscv64-latest.abi-update.args | 15 ++++--- > ...fault-models.riscv64-latest.abi-update.xml | 26 +++++------- > ...64-virt-default-models.riscv64-latest.args | 15 ++++--- > ...v64-virt-default-models.riscv64-latest.xml | 26 +++++------- > ...-fallback-virt-riscv64.riscv64-latest.args | 35 ---------------- > ...t-fallback-virt-riscv64.riscv64-latest.xml | 41 ------------------- > ...ntroller-default-fallback-virt-riscv64.xml | 1 - > ...r-default-virt-riscv64.riscv64-latest.args | 5 +-- > ...er-default-virt-riscv64.riscv64-latest.xml | 12 ++---- > tests/qemuxmlconftest.c | 5 --- > 11 files changed, 44 insertions(+), 140 deletions(-) > delete mode 100644 > tests/qemuxmlconfdata/usb-controller-default-fallback-virt-riscv64.riscv64-latest.args > delete mode 100644 > tests/qemuxmlconfdata/usb-controller-default-fallback-virt-riscv64.riscv64-latest.xml > delete mode 120000 > tests/qemuxmlconfdata/usb-controller-default-fallback-virt-riscv64.xml
Reviewed-by: Peter Krempa <pkre...@redhat.com>
