On Fri, May 26, 2023 at 04:42:57AM -0400, Andrea Bolognani wrote: > On Fri, May 26, 2023 at 10:34:36AM +0200, Andrew Jones wrote: > > On Fri, May 26, 2023 at 03:49:11AM -0400, Andrea Bolognani wrote: > > > So, are edk2 users the only ones who would (temporarily) need to > > > manually turn ACPI off if virt-manager started enabling it by > > > default? > > > > I assume so, but I'm not tracking firmware status. If the firmware > > doesn't extract the ACPI tables from QEMU and present them to the > > guest (afaik only edk2 does that), then the guest kernel falls back > > to DT, which is why it's working for you. > > > > I suppose we should wait until Linux merges the ACPI patches, before > > adding RISC-V to the libvirt capabilities ACPI list. > > That sounds reasonable to me, but note that 1) the libvirt change > might take a while to propagate to distros and 2) someone will have > to remind me to prepare such a patch when the time comes ;)
Initial ACPI support will probably be merged for 6.4. So maybe it is time to get the libvirt side of things going. > > > Then, is it > > possible to use something like libosinfo to inform virt-manager > > when it should enable ACPI and when not? Later distro images, with > > later kernels, will want to use ACPI by default, but older images > > will still need to use DT. > > Something like that would definitely be possible, but I don't think > the scaffolding for it exists at the moment, so someone would have to > wire it up across the stack. Given how relatively immature the RISC-V > distro ecosystem is at the moment, I think it's fine to do nothing > and wait for the problem to go away on its own :) WFM Thanks, drew
