qemu-riscv
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v4 0/3] hw/riscv/virt: pflash improvements


From: Andrea Bolognani
Subject: Re: [PATCH v4 0/3] hw/riscv/virt: pflash improvements
Date: Thu, 30 May 2024 04:37:56 -0700

On Mon, Nov 20, 2023 at 08:06:19PM GMT, Sunil V L wrote:
> On Mon, Nov 20, 2023 at 02:29:28PM +0000, Andrea Bolognani wrote:
> > On Fri, May 26, 2023 at 11:10:12AM +0200, Andrew Jones 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.
> >
> > Randomly remembered about this. Did ACPI support make it into 6.4
> > after all? Is now a good time to change libvirt?
>
> Hi Andrea,
>
> Not yet. While basic ACPI changes are merged, the interrupt controller
> support is still going on. Looks like it will take few merge windows to
> get ACPI fully supported. So, we still need to wait for libvirt change.

Hey,

I've been working on making RISC-V support a bit smoother across the
virtualization stack recently, and I just so happened to remember
that this topic was still pending.

I've tried manually switching ACPI on for an existing Fedora RISC-V
guest running under TCG and booting via UEFI, which promptly made it
stop working, so I assume the necessary bits haven't made it into the
kernel yet.

Is anyone actually tracking that work? We've been waiting for it to
land for a fairly long time at this point...

Thanks.

-- 
Andrea Bolognani / Red Hat / Virtualization




reply via email to

[Prev in Thread] Current Thread [Next in Thread]