Re: [PATCH 27/31] qemu: Use qemu-xhci by default on RISC-V

2025-09-19 Thread Peter Krempa via Devel
On Fri, Sep 19, 2025 at 08:10:41 -0700, Andrea Bolognani wrote: > On Fri, Sep 19, 2025 at 11:23:14AM +0200, Peter Krempa wrote: > > On Tue, Aug 19, 2025 at 18:22:31 +0200, Andrea Bolognani via Devel wrote: > > > +if (ARCH_IS_LOONGARCH(def->os.arch) || > > > +qemuDomainIsRISCVVirt(def))

Re: [PATCH 27/31] qemu: Use qemu-xhci by default on RISC-V

2025-09-19 Thread Andrea Bolognani via Devel
On Fri, Sep 19, 2025 at 11:23:14AM +0200, Peter Krempa wrote: > On Tue, Aug 19, 2025 at 18:22:31 +0200, Andrea Bolognani via Devel wrote: > > +if (ARCH_IS_LOONGARCH(def->os.arch) || > > +qemuDomainIsRISCVVirt(def)) { > > /* Use qemu-xhci (USB3) for modern architectures */ > >

Re: [PATCH 27/31] qemu: Use qemu-xhci by default on RISC-V

2025-09-19 Thread Peter Krempa via Devel
On Tue, Aug 19, 2025 at 18:22:31 +0200, Andrea Bolognani via Devel wrote: > Currently we fall back to the x86-derived default of piix3-uhci, > which is a USB1 controller that's not virtualization-friendly > and overall a terrible choice for a modern architecture. The > fact that we didn't choose a

[PATCH 27/31] qemu: Use qemu-xhci by default on RISC-V

2025-08-19 Thread Andrea Bolognani via Devel
Currently we fall back to the x86-derived default of piix3-uhci, which is a USB1 controller that's not virtualization-friendly and overall a terrible choice for a modern architecture. The fact that we didn't choose a better default when RISC-V support was introduced was an oversight which is now ad